Re: Help with "gpg -d ... | pg_restore ..." with unimportant pg_restore errors - Mailing list pgsql-general

From raf
Subject Re: Help with "gpg -d ... | pg_restore ..." with unimportant pg_restore errors
Date
Msg-id ZtfIYOzklqtEvIOs@raf.org
Whole thread Raw
In response to Re: Help with "gpg -d ... | pg_restore ..." with unimportant pg_restore errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Sep 03, 2024 at 10:28:44PM -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> raf <postgres@raf.org> writes:
> > On Tue, Sep 03, 2024 at 06:43:22PM -0700, "David G. Johnston" <david.g.johnston@gmail.com> wrote:
> >> You specified “-1” so I don’t get why you believe pg_restore should be
> >> continuing to execute in the face of the SQL error.
> 
> > The reason I believe pg_restore should be continuing to execute in the face of
> > the SQL error is because I didn't supply the -e option which is described
> > thusly in the pg_restore manual entry:
> 
> But you'd better also read the para about -1:
> 
>   -1
>   --single-transaction
>     Execute the restore as a single transaction (that is, wrap the
>     emitted commands in BEGIN/COMMIT). This ensures that either all
>     the commands complete successfully, or no changes are
>     applied. This option implies --exit-on-error.
> 
>             regards, tom lane
> 

Yes, I saw that. Many thanks. All good now.

cheer,
raf




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Help with "gpg -d ... | pg_restore ..." with unimportant pg_restore errors
Next
From: Sam Son
Date:
Subject: Re: Issue with Restore dump with plpythonu, plpython3u installed on postgres16