Re: synchronized snapshots

From: Joachim Wieland <joe(at)mcknight(dot)de>
To: Jim Nasby <jim(at)nasby(dot)net>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: synchronized snapshots
Date: 2011-08-15 22:46:14
Message-ID: CACw0+13N-XuT-zi7WkRTK1LKZjsNt_sowMu+iXdwP9K+96=HVw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 15, 2011 at 6:09 PM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> I suspect that all the other cases of BEGIN failing would be syntax errors, so
> you would immediately know in testing that something was wrong. A missing file
> is definitely not a syntax error, so we can't really depend on user testing to ensure
> this is handled correctly. IMO, that makes it critical that that error puts us in an
> aborted transaction.

Why can we not just require the user to verify if his BEGIN query
failed or succeeded?
Is that really too much to ask for?

Also see what Robert wrote about proxies in between that keep track of
the transaction
state. Consider they see a BEGIN query that fails. How would they know
if the session
is now in an aborted transaction or not in a transaction at all?

Joachim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2011-08-15 23:26:32 Re: our buffer replacement strategy is kind of lame
Previous Message Peter Geoghegan 2011-08-15 22:43:18 Re: Should we have an optional limit on the recursion depth of recursive CTEs?