Re: Avoid too prominent use of "backup" on pg_dump man page
От
Laurenz Albe
Тема
Re: Avoid too prominent use of "backup" on pg_dump man page
Дата
Msg-id
cce486c8a7666b305aa8de4e5f7f3a0570a39400.camel@cybertec.at
Ответ на
Re: Avoid too prominent use of "backup" on pg_dump man page (Daniel Gustafsson)
Список
Дерево обсуждения
Avoid too prominent use of "backup" on pg_dump man page Peter Eisentraut <peter@eisentraut.org>
Re: Avoid too prominent use of "backup" on pg_dump man page Daniel Gustafsson <daniel@yesql.se>
Re: Avoid too prominent use of "backup" on pg_dump man page Laurenz Albe <laurenz.albe@cybertec.at>
Re: Avoid too prominent use of "backup" on pg_dump man page Peter Eisentraut <peter@eisentraut.org>
On Thu, 2024-05-30 at 08:21 +0200, Daniel Gustafsson wrote: > No objections to using export over backup, but it does make the use of > "restore" feel awkward as that's generally an operation on a backup and not an > export. > > - least one schema/table in the backup file. > + least one schema/table in the file to be restored. > > Would it make sense to use "import" in some cases instead? What about calling it "dump file" instead of "file to be restored"? Yours, Laurenz Albe
В списке pgsql-docs по дате отправления