Re: proposal: possibility to read dumped table's name from file
От | Erik Rijkers |
---|---|
Тема | Re: proposal: possibility to read dumped table's name from file |
Дата | |
Msg-id | 13a277d9-9066-1aff-1c1c-50a96eef3419@xs4all.nl обсуждение исходный текст |
Ответ на | Re: proposal: possibility to read dumped table's name from file (Erik Rijkers <er@xs4all.nl>) |
Список | pgsql-hackers |
Op 12-09-2022 om 16:00 schreef Erik Rijkers: > Op 12-09-2022 om 09:58 schreef Daniel Gustafsson: >>> On 9 Sep 2022, at 11:00, Andrew Dunstan <andrew@dunslane.net> wrote: >>> >>>> On Sep 9, 2022, at 5:53 PM, John Naylor >>>> <john.naylor@enterprisedb.com> wrote: > >>>> [v4-0001-Add-include-exclude-filtering-via-file-in-pg_dump.patch] > > I noticed that pg_restore --filter cannot, or at last not always, be > used with the same filter-file that was used to produce a dump with > pg_dump --filter. > > Is that as designed? It seems a bit counterintuitive. It'd be nice if > that could be fixed. Admittedly, the 'same' problem in pg_restore -t, > also less than ideal. > > (A messy bashdemo below) I hope the issue is still clear, even though in the bash I sent, I messed up the dumpfile name (i.e., in the bash that I sent the pg_dump creates another dump name than what is given to pg_restore. They should use the same dumpname, obviously) > > thanks, > > Erik Rijkers
В списке pgsql-hackers по дате отправления: