Re: Avoid too prominent use of "backup" on pg_dump man page

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Avoid too prominent use of "backup" on pg_dump man page
Date: 2024-05-30 06:21:16
Message-ID: 57182DC3-418C-44FD-97A6-80EE87B08A2E@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

> On 30 May 2024, at 01:11, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:

> Suggestions for word-smithing welcome.

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?

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Marcel Hofstetter 2024-05-30 11:14:59 Re: 17beta1 source download does not include docs & manpages
Previous Message Peter Smith 2024-05-30 00:50:49 Re: Ambiguous description on new columns