BUG #15977: Inconsistent behavior in chained transactions

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: emuser20140816(at)gmail(dot)com
Subject: BUG #15977: Inconsistent behavior in chained transactions
Date: 2019-08-25 06:11:05
Message-ID: 15977-f4eb49ebdcacc65b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

The following bug has been logged on the website:

Bug reference: 15977
Logged by: mtlh kdvt
Email address: emuser20140816(at)gmail(dot)com
PostgreSQL version: 12beta3
Operating system: Windows
Description:

When a ROLLBACK AND CHAIN command is executed in the implicit transaction
block, a new transaction will be started:
db=# ROLLBACK AND CHAIN;
WARNING: there is no transaction in progress
ROLLBACK
db=# ROLLBACK AND CHAIN;
ROLLBACK

However, a COMMIT AND CHAIN command won't start a new transaction:
db=# COMMIT AND CHAIN;
WARNING: there is no transaction in progress
COMMIT
db=# COMMIT AND CHAIN;
WARNING: there is no transaction in progress
COMMIT

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Fabien COELHO 2019-08-25 09:11:09 Re: BUG #15977: Inconsistent behavior in chained transactions
Previous Message Andres Freund 2019-08-24 22:54:01 Re: PostgreSQL12 crash bug report

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-08-25 07:02:23 Re: mingw32 floating point diff
Previous Message Peter Geoghegan 2019-08-25 03:15:34 Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev)