Re: Error on failed COMMIT

Dave Cramer <davecramer@postgres.rocks>

From: Dave Cramer <davecramer@postgres.rocks>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Tony Locke <tlocke@tlocke.org.uk>, 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-11-10T16:53:20Z
Lists: pgsql-hackers

Attachments

On Mon, 9 Nov 2020 at 16:26, Dave Cramer <davecramer@postgres.rocks> wrote:

>
>
> On Wed, 30 Sep 2020 at 18:14, Andrew Dunstan <
> andrew.dunstan@2ndquadrant.com> wrote:
>
>>
>> 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
>>
>
>
> Attached is a rebased patch with fixes for the isolation tests
>
>

>
> Dave Cramer
> www.postgres.rocks
>