Re: Avoid too prominent use of "backup" on pg_dump man page - Mailing list pgsql-docs

From Laurenz Albe
Subject Re: Avoid too prominent use of "backup" on pg_dump man page
Date
Msg-id cce486c8a7666b305aa8de4e5f7f3a0570a39400.camel@cybertec.at
Whole thread Raw
In response to Re: Avoid too prominent use of "backup" on pg_dump man page  (Daniel Gustafsson <daniel@yesql.se>)
List 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



pgsql-docs by date:

Previous
From: vignesh C
Date:
Subject: Re: Ambiguous description on new columns
Next
From: "Euler Taveira"
Date:
Subject: Re: 28.4.4. Progress Reporting phase status