Re: Error on failed COMMIT - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: Error on failed COMMIT
Date
Msg-id CADK3HHJrJecqy4gCLOi3fuk9rd114rQmZvbP0KzHhm-dOLRj=Q@mail.gmail.com
Whole thread Raw
In response to Re: Error on failed COMMIT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Error on failed COMMIT  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers



On Fri, 14 Feb 2020 at 15:07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Dave Cramer <davecramer@postgres.rocks> writes:
> On Fri, 14 Feb 2020 at 14:37, Robert Haas <robertmhaas@gmail.com> wrote:
>> I'm not trying to deny that you might find some other server behavior
>> more convenient. You might. And, to Vik's original point, it might be
>> more compliant with the spec, too. But since changing that would have
>> a pretty big blast radius at this stage, I think it's worth trying to
>> make things work as well as they can with the server behavior that we
>> already have. And I don't really see anything preventing the driver
>> from doing that technically. I don't understand the idea that the
>> driver is somehow not allowed to notice the command tag.

> We have the same blast radius.
> I have offered to make the behaviour requested dependent on a configuration
> parameter but apparently this is not sufficient.

Nope, that is absolutely not happening. 

I should have been more specific. 

I offered to make the behaviour in the JDBC driver dependent on a configuration parameter

Dave Cramer
www.postgres.rocks

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Error on failed COMMIT
Next
From: Alvaro Herrera
Date:
Subject: Re: Error on failed COMMIT