Re: Information on savepoint requirement within transctions

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Zenz <robert(dot)zenz(at)sibvisions(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Information on savepoint requirement within transctions
Date: 2018-01-29 16:09:41
Message-ID: CAKFQuwbKQM8OX8_4OrSdVqv-o0MMru4P40i=X7YUfsSutqmu3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jan 29, 2018 at 9:00 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > On Mon, Jan 29, 2018 at 8:33 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steve Crawford 2018-01-29 16:12:18 Re: Which specific flags to use for bash client applications for DaVinci Resolve?
Previous Message Thomas Boussekey 2018-01-29 16:01:03 Re: PG Sharding