Re: BUG #16732: pg_dump creates broken backups - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16732: pg_dump creates broken backups
Date
Msg-id 1546649.1605981453@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #16732: pg_dump creates broken backups  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16736: SCRAM authentication is not supported by this driver
Next
From: Sofoklis Papasofokli
Date:
Subject: Re: BUG #16730: Create table like with inheritance and self referencing index