From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Zsolt Ero <zsolt.ero@gmail.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16732: pg_dump creates broken backups
Date: Sat, 21 Nov 2020 12:57:33 -0500
Message-ID: <1546649.1605981453@sss.pgh.pa.us> (raw)
In-Reply-To: <20201121170638.GA10288@alvherre.pgsql>
References: <20201121170638.GA10288@alvherre.pgsql>
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Why do you do that? It seems much easier to produce a complete dump,
> then obtain the --list from it, do "grep -v" of the TABLE DATA element
> for that table, then give that file to pg_restore. It would restore
> everything in the right order, including that table's definition, but
> excluding that table's data.
Yeah, it's clearly possible to dodge the issue by using a different
dump/restore procedure. Still, this procedure is not obviously
incorrect, so it'd be nice if pg_restore coped better.
regards, tom lane
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: tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, zsolt.ero@gmail.com, david.g.johnston@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16732: pg_dump creates broken backups
In-Reply-To: <1546649.1605981453@sss.pgh.pa.us>
* 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