From: Tom Lane <tgl@sss.pgh.pa.us>
To: Holger Jakobs <holger@jakobs.com>
cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: psql terminates on first error
In-reply-to: <572addf0-5116-cec0-77fb-9a0ba0161240@jakobs.com>
References: <572addf0-5116-cec0-77fb-9a0ba0161240@jakobs.com>
Comments: In-reply-to Holger Jakobs <holger@jakobs.com>
	message dated "Thu, 02 Mar 2023 12:53:19 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1897763.1677767610.1@sss.pgh.pa.us>
Date: Thu, 02 Mar 2023 09:33:30 -0500
Message-ID: <1897764.1677767610@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1897764.1677767610%40sss.pgh.pa.us>
Precedence: bulk

Holger Jakobs <holger@jakobs.com> writes:
> While trying to transfer data from one instance to another using 
> pg_dumpall and psql, the psql stopped on first error, causing pg_dumpall 
> to terminate as well.
> This behaviour was seen on Windows (EDB installer), but is different on 
> Linux.
> Only when using an option -c "\set ON_ERROR_STOP false" (plus -f - of 
> course to continue reading) psql continued after first error.
> Not even the option -v ON_ERROR_STOP=0 helped.
> Why is the behaviour between Linux and Windows different? This is not 
> reflected in the documentation.

It shouldn't be different.  However, this report would be trivially
explained if your Windows machine has an %APPDATA%\postgresql\psqlrc.conf
file that turns ON_ERROR_STOP on.  You could try invoking psql with
the -X command line switch to prevent reading that.

			regards, tom lane