Re: Avoid too prominent use of "backup" on pg_dump man page
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Daniel Gustafsson <daniel@yesql.se>, Peter Eisentraut
<peter@eisentraut.org>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Date: 2024-05-31T08:24:36Z
Lists: pgsql-docs
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
Commits
-
doc: Avoid too prominent use of "backup" on pg_dump man page
- 4f29394ea941 18.0 landed