Re: BUG #15977: Inconsistent behavior in chained transactions

From: fn ln <emuser20140816(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15977: Inconsistent behavior in chained transactions
Date: 2019-09-09 09:32:09
Message-ID: CA+99BHpqbB9m0t=Tuc6oBN-uSCLdgB1j-zXk=fNHPbq7N5k7xw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

It looks good now. Thank you again.

2019年9月9日(月) 17:43 Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>:

> On 2019-09-09 05:58, fn ln wrote:
> > Confirmed. Thank you all for your help.
> >
> > The only concern is that this test:
> >
> > SET TRANSACTION READ WRITE\; COMMIT AND CHAIN; -- error
> > SHOW transaction_read_only;
> >
> > SET TRANSACTION READ WRITE\; ROLLBACK AND CHAIN; -- error
> > SHOW transaction_read_only;
> >
> > makes more sense with READ ONLY because default_transaction_read_only is
> > off at this point.
>
> Oh you're right. Fixed.
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Petar Masev 2019-09-09 10:12:30 RE: Postgres 11.5.1 failed installation
Previous Message Sandeep Thakkar 2019-09-09 09:22:39 Re: Postgres 11.5.1 failed installation

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-09-09 10:17:38 Re: refactoring - share str2*int64 functions
Previous Message Pavel Stehule 2019-09-09 09:25:32 patch: psql - enforce constant width of last column