Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvhAC-0008V9-FK for pgsql-bugs@arkaria.postgresql.org; Mon, 30 May 2022 15:18:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nvhAB-0007Jt-9R for pgsql-bugs@arkaria.postgresql.org; Mon, 30 May 2022 15:18:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvhAB-0007Jj-1D for pgsql-bugs@lists.postgresql.org; Mon, 30 May 2022 15:18:35 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvhA6-0006BG-9e for pgsql-bugs@lists.postgresql.org; Mon, 30 May 2022 15:18:34 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 4LBfF04sMtz3F12 for ; Mon, 30 May 2022 17:18:28 +0200 (CEST) Date: Mon, 30 May 2022 17:18:28 +0200 From: Christoph Berg To: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17504: psql --single-transaction -vON_ERROR_STOP=1 still commits after client-side error Message-ID: References: <17504-76b68018e130415e@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17504-76b68018e130415e@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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