Fix psql's ON_ERROR_ROLLBACK so that it handles COMMIT AND CHAIN.
authorFujii Masao <fujii@postgresql.org>
Fri, 19 Feb 2021 13:01:25 +0000 (22:01 +0900)
committerFujii Masao <fujii@postgresql.org>
Fri, 19 Feb 2021 13:01:25 +0000 (22:01 +0900)
commitfe06819f105ccea52c12d418c8dbaaaa54377e96
treed1cbef17e0709627dd19a6599eed09572ef191e4
parent8a55cb5ba9655ffb1cf0a3042aaa6f5eef8c5a85
Fix psql's ON_ERROR_ROLLBACK so that it handles COMMIT AND CHAIN.

When ON_ERROR_ROLLBACK is enabled, psql releases a temporary savepoint
if it's idle in a valid transaction block after executing a query. But psql
doesn't do that after RELEASE or ROLLBACK is executed because a temporary
savepoint has already been destroyed in that case.

This commit changes psql's ON_ERROR_ROLLBACK so that it doesn't release
a temporary savepoint also when COMMIT AND CHAIN is executed. A temporary
savepoint doesn't need to be released in that case because
COMMIT AND CHAIN also destroys any savepoints defined within the transaction
to commit. Otherwise psql tries to release the savepoint that
COMMIT AND CHAIN has already destroyed and cause an error
"ERROR:  savepoint "pg_psql_temporary_savepoint" does not exist".

Back-patch to v12 where transaction chaining was added.

Reported-by: Arthur Nascimento
Author: Arthur Nascimento
Reviewed-by: Fujii Masao, Vik Fearing
Discussion: https://postgr.es/m/16867-3475744069228158@postgresql.org
src/bin/psql/common.c