From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Daniel Gustafsson <daniel@yesql.se>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Avoid too prominent use of "backup" on pg_dump man page
Date: Fri, 31 May 2024 10:24:36 +0200
Message-ID: <cce486c8a7666b305aa8de4e5f7f3a0570a39400.camel@cybertec.at> (raw)
In-Reply-To: <57182DC3-418C-44FD-97A6-80EE87B08A2E@yesql.se>
References: <70b48475-7706-4268-990d-fd522b038d96@eisentraut.org>
<57182DC3-418C-44FD-97A6-80EE87B08A2E@yesql.se>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, daniel@yesql.se, peter@eisentraut.org
Subject: Re: Avoid too prominent use of "backup" on pg_dump man page
In-Reply-To: <cce486c8a7666b305aa8de4e5f7f3a0570a39400.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox