From: Peter Eisentraut <peter@eisentraut.org>
To: Laurenz Albe <laurenz.albe@cybertec.at>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Avoid too prominent use of "backup" on pg_dump man page
Date: Wed, 31 Jul 2024 08:14:28 +0200
Message-ID: <6ac73ca9-9559-4df5-81c7-ebad848fd6d5@eisentraut.org> (raw)
In-Reply-To: <cce486c8a7666b305aa8de4e5f7f3a0570a39400.camel@cybertec.at>
References: <70b48475-7706-4268-990d-fd522b038d96@eisentraut.org>
<57182DC3-418C-44FD-97A6-80EE87B08A2E@yesql.se>
<cce486c8a7666b305aa8de4e5f7f3a0570a39400.camel@cybertec.at>
On 31.05.24 10:24, Laurenz Albe wrote:
> 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"?
I forgot about this one for a bit. I committed it now as I had proposed
it. The pg_restore man page consistently talks about "restoring" a
file, so this change makes that more consistent. Introducing another
verb would require more changes to properly introduce and explain it,
which seems out of scope for this particular patch.
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: peter@eisentraut.org, laurenz.albe@cybertec.at, daniel@yesql.se
Subject: Re: Avoid too prominent use of "backup" on pg_dump man page
In-Reply-To: <6ac73ca9-9559-4df5-81c7-ebad848fd6d5@eisentraut.org>
* 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