Re: Information on savepoint requirement within transctions - Mailing list pgsql-general

From David G. Johnston
Subject Re: Information on savepoint requirement within transctions
Date
Msg-id CAKFQuwbKQM8OX8_4OrSdVqv-o0MMru4P40i=X7YUfsSutqmu3g@mail.gmail.com
Whole thread Raw
In response to Re: Information on savepoint requirement within transctions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, Jan 29, 2018 at 9:00 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Mon, Jan 29, 2018 at 8:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What we do have though is client-side support for appropriate behaviors.
>> In psql, see the AUTOCOMMIT and ON_ERROR_ROLLBACK control variables.

> Not quite the same.  I think what people probably want is for psql to
> recognize it is in a transaction and before sending a command to the server
> for processing to precede it by sending "SAVEPOINT random()".  Then, before
> returning the result of the command to the user issue either "RELEASE
> SAVEPOINT" or "ROLLBACK TO SAVEPOINT" depending on whether the command
> succeeded or failed.  Then report the result to the user.

Which part of that isn't implemented by ON_ERROR_ROLLBACK?

​My turn to fail to re-read the docs :(

David J.

pgsql-general by date:

Previous
From: Thomas Boussekey
Date:
Subject: Re: PG Sharding
Next
From: Steve Crawford
Date:
Subject: Re: Which specific flags to use for bash client applications forDaVinci Resolve?