Re: BUG #15977: Inconsistent behavior in chained transactions
| От | fn ln |
|---|---|
| Тема | Re: BUG #15977: Inconsistent behavior in chained transactions |
| Дата | |
| Msg-id | CA+99BHqxMfUyZcSh2B=ni5db83U1qtgX7bv+U7iXRbJqkTVFJg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #15977: Inconsistent behavior in chained transactions (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
| Ответы |
Re: BUG #15977: Inconsistent behavior in chained transactions
|
| Список | pgsql-hackers |
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;
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.
2019年9月9日(月) 5:27 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
On 2019-09-07 18:32, fn ln wrote:
>> Missed them somehow. But I don't think they're quite sufficient. I think
>> at least we also need tests that test things like multi-statement
>> exec_simple-query() *with* explicit transactions and chaining.
> Added a few more tests for that.
I committed this patch with some cosmetic changes and documentation updates.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: