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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-31 08:24:36
Message-ID: cce486c8a7666b305aa8de4e5f7f3a0570a39400.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Euler Taveira 2024-06-03 20:15:25 Re: 28.4.4. Progress Reporting phase status
Previous Message vignesh C 2024-05-31 03:28:16 Re: Ambiguous description on new columns