From: Christoph Berg <christoph.berg@credativ.de>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
Date: Mon, 30 May 2022 17:18:28 +0200
Message-ID: <YpTgRGknCLBopP8C@msg.df7cb.de> (raw)
In-Reply-To: <17504-76b68018e130415e@postgresql.org>
References: <17504-76b68018e130415e@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: christoph.berg@credativ.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error
In-Reply-To: <YpTgRGknCLBopP8C@msg.df7cb.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox