Re: BUG #16732: pg_dump creates broken backups
| От | Alvaro Herrera |
|---|---|
| Тема | Re: BUG #16732: pg_dump creates broken backups |
| Дата | |
| Msg-id | 20201121170638.GA10288@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: BUG #16732: pg_dump creates broken backups (Zsolt Ero <zsolt.ero@gmail.com>) |
| Ответы |
Re: BUG #16732: pg_dump creates broken backups
Re: BUG #16732: pg_dump creates broken backups |
| Список | pgsql-bugs |
On 2020-Nov-21, Zsolt Ero wrote: > I didn't state why I'm doing all this: basically all I'd like to do is > exclude a table when restoring data. > The only way I managed to do this was to grep -v the list file before data > only restore. 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.
В списке pgsql-bugs по дате отправления: