Date: Thu, 2 Mar 2023 14:45:08 +0100 (CET)
From: Erik Wienhold <ewie@ewie.name>
To: Holger Jakobs <holger@jakobs.com>, pgsql-admin@lists.postgresql.org
Message-ID: <1402808643.90840.1677764708832@office.mailbox.org>
In-Reply-To: <ed1d66b8-1250-1e2d-cacf-b81aa9433cc8@jakobs.com>
References: <572addf0-5116-cec0-77fb-9a0ba0161240@jakobs.com>
 <453307953.83682.1677760371729@office.mailbox.org>
 <c2f5c47e-f603-a54a-7ad1-2d780857523e@jakobs.com>
 <1b41a19f-5672-e185-f3ec-df96c6dcbae7@gmx.net>
 <ed1d66b8-1250-1e2d-cacf-b81aa9433cc8@jakobs.com>
Subject: Re: psql terminates on first error
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
Archived-At: 
 <https://www.postgresql.org/message-id/1402808643.90840.1677764708832%40office.mailbox.org>
Precedence: bulk

> On 02/03/2023 14:30 CET Holger Jakobs <holger@jakobs.com> wrote:
>
> Am 02.03.23 um 13:48 schrieb Thomas Kellerer:
> > Holger Jakobs schrieb am 02.03.2023 um 13:44:
> >>>> Only when using an option -c "\set ON_ERROR_STOP false" (plus -f - o=
f
> >>>> course to continue reading) psql continued after first error.
> >>> Do you use PowerShell and pipe pg_dumpall into psql?=C2=A0 The first =
thing
> >>> that comes to my mind when reading Postgres+Windows is that PowerShel=
l
> >>> up to version 5.1 converts stdout to UTF-16LE.=C2=A0 This already tri=
pped me
> >>> up in past with pg_dump and psql.
> >> No, it was in cmd.exe or in bash
> > I find using pipes with the Postgres command line tools on Windows
> > unreliable in general (including cmd.exe). So if you did use
> > redirection/pips, try without.
>
> Whether I use pipes or writing stdout of pg_dumpall to a file and=20
> reading back with psql from the file made no difference.

Try pg_dumpall with option -f instead of redirecting stdout:

=09pg_dumpall -f dump.sql
=09psql -f dump.sql

Redirecting stdout to an intermediate file should have the same effect as
piping to psql.

And what error do you get from psql?

--
Erik