| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Zsolt Ero <zsolt(dot)ero(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16732: pg_dump creates broken backups |
| Date: | 2020-11-21 17:57:33 |
| Message-ID: | 1546649.1605981453@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sofoklis Papasofokli | 2020-11-21 22:27:16 | Re: BUG #16730: Create table like with inheritance and self referencing index |
| Previous Message | Tom Lane | 2020-11-21 17:44:55 | Re: BUG #16736: SCRAM authentication is not supported by this driver |