Re: Error on failed COMMIT
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Dave Cramer <davecramer@postgres.rocks>, Tony Locke <tlocke@tlocke.org.uk>
Cc: Shay Rojansky <roji@roji.org>, Bruce Momjian <bruce@momjian.us>,
Robert Haas <robertmhaas@gmail.com>, Vik Fearing <vik@postgresfriends.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Laurenz Albe <laurenz.albe@cybertec.at>,
Vladimir Sitnikov <sitnikov.vladimir@gmail.com>,
"Haumacher, Bernhard" <haui@haumacher.de>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-09-30T22:14:52Z
Lists: pgsql-hackers
On 8/4/20 12:19 PM, Dave Cramer wrote: > Attached is the rebased patch for consideration. > > It's a bit sad this has been hanging around so long without attention. The previous discussion seems to give the patch a clean bill of health for most/all of the native drivers. Are there any implications for libpq based drivers such as DBD::Pg and psycopg2? How about for ecpg? cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services