Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
Christoph Berg <christoph.berg@credativ.de>
From: Christoph Berg <christoph.berg@credativ.de>
To: pgsql-bugs@lists.postgresql.org
Date: 2022-05-30T15:18:28Z
Lists: pgsql-bugs
Re: PG Bug reporting form > The problem is not limited to \copy; \i has the same problem. > A workaround is to drop -1, and use an explicit transaction in the script. \connect correctly aborts the whole operation. I would suggest that all client-side errors should be handled as fatal when both --single-transaction and -vON_ERROR_STOP=1 are in effect. Christoph
Commits
-
Tweak behavior of psql --single-transaction depending on ON_ERROR_STOP
- a3ff08e0b08d 15.0 landed
-
Doc: remove a04ccf6df from release notes, now that it's reverted.
- 18f66a1a91bd 14.4 landed
-
Revert "Fix psql's single transaction mode on client-side errors with -c/-f switches".
- f25b5519c99a 14.4 landed
- db713aa7fcbe 10.22 landed
- aaa88d3828c3 11.17 landed
- 3f7f06738529 13.8 landed
- 030da9b6fd52 12.12 landed
-
Fix psql's single transaction mode on client-side errors with -c/-f switches
- c3df4d53ca4a 10.22 landed
- b0bd9327dd74 11.17 landed
- 0a1e4f0ca788 12.12 landed
- b364cfdfaf6b 13.8 landed
- a04ccf6dfb4a 14.4 landed
- 157f8739ad18 15.0 landed