Re: synchronized snapshots - Mailing list pgsql-hackers

From Joachim Wieland
Subject Re: synchronized snapshots
Date
Msg-id CACw0+13N-XuT-zi7WkRTK1LKZjsNt_sowMu+iXdwP9K+96=HVw@mail.gmail.com
Whole thread Raw
In response to Re: synchronized snapshots  (Jim Nasby <jim@nasby.net>)
Responses Re: synchronized snapshots
Re: synchronized snapshots
List pgsql-hackers
On Mon, Aug 15, 2011 at 6:09 PM, Jim Nasby <jim@nasby.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


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Should we have an optional limit on the recursion depth of recursive CTEs?
Next
From: Jim Nasby
Date:
Subject: Re: our buffer replacement strategy is kind of lame