From: Laurenz Albe <laurenz.albe@cybertec.at>
To: carl@msupply.foundation
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
Date: Thu, 14 Mar 2024 06:58:28 +0100
Message-ID: <a07a7bc4d0442e7dadce1ec57c014c2ebced13ee.camel@cybertec.at> (raw)
In-Reply-To: <18392-142078457489d3a5@postgresql.org>
References: <18392-142078457489d3a5@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: laurenz.albe@cybertec.at, carl@msupply.foundation, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
In-Reply-To: <a07a7bc4d0442e7dadce1ec57c014c2ebced13ee.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox