Re: Error on failed COMMIT
Dave Cramer <davecramer@postgres.rocks>
From: Dave Cramer <davecramer@postgres.rocks>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, "Haumacher,
Bernhard" <haui@haumacher.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-02-14T20:11:42Z
Lists: 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 > >