Re: Error on failed COMMIT

From: Dave Cramer <davecramer(at)postgres(dot)rocks>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Shay Rojansky <roji(at)roji(dot)org>, "Haumacher, Bernhard" <haui(at)haumacher(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Error on failed COMMIT
Date: 2020-03-17 23:32:00
Message-ID: CADK3HHLuorK_Dx2QFD_o0RXa2oBkx2uOmOx3GH0NnURT_xk9Cw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 17 Mar 2020 at 19:23, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> On Tue, Mar 17, 2020 at 07:15:05PM -0400, Dave Cramer wrote:
> > On Tue, 17 Mar 2020 at 16:47, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Third, the idea that individual interfaces, e.g. JDBC, should throw
> an
> > error in this case while the server just changes the COMMIT return
> tag
> > to ROLLBACK is confusing. People regularly test SQL commands in the
> > server before writing applications or while debugging, and a behavior
> > mismatch would cause confusion.
> >
> >
> > I'm not sure what you mean by this. The server would throw an error.
>
> I am saying it is not wise to have interfaces behaving differently than
> the server, for the reasons stated above.
>
> Agreed and this is why I think it is important for the server to be
defining the behaviour instead of each interface deciding how to handle
this situation.

Dave Cramer
www.postgres.rocks

>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2020-03-17 23:32:18 Re: Berserk Autovacuum (let's save next Mandrill)
Previous Message Bruce Momjian 2020-03-17 23:23:30 Re: Error on failed COMMIT