Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update - Mailing list pgsql-bugs

From Laurenz Albe
Subject Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
Date
Msg-id a07a7bc4d0442e7dadce1ec57c014c2ebced13ee.camel@cybertec.at
Whole thread Raw
In response to BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
List pgsql-bugs
On Thu, 2024-03-14 at 03:06 +0000, PG Bug reporting form wrote:
> PostgreSQL version: 14.11
> Operating system:   MacOS
>
> We regularly save snapshots of our app state using pg_dump and restore them
> with pg_restore. However, after the latest update (12.18 etc), we can no
> longer use pg_restore to restore the database -- it  just throws a bunch of
> errors, mainly to do with tables not existing (that should exist).

Please don't keep us guessing and show us the errors.  The first couple of
error messages will be enough, the remainder is often a consequence of those.

Yours,
Laurenz Albe



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
Next
From: Carl Smith
Date:
Subject: Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update