From: | raf <postgres(at)raf(dot)org> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Help with "gpg -d ... | pg_restore ..." with unimportant pg_restore errors |
Date: | 2024-09-04 02:39:28 |
Message-ID: | ZtfIYOzklqtEvIOs@raf.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 03, 2024 at 10:28:44PM -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> raf <postgres(at)raf(dot)org> writes:
> > On Tue, Sep 03, 2024 at 06:43:22PM -0700, "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Son | 2024-09-04 10:48:00 | Re: Issue with Restore dump with plpythonu, plpython3u installed on postgres16 |
Previous Message | Tom Lane | 2024-09-04 02:28:44 | Re: Help with "gpg -d ... | pg_restore ..." with unimportant pg_restore errors |