From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | axel(dot)kluener(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: "Restore" vs. "Reload" |
Date: | 2022-07-21 18:55:48 |
Message-ID: | YtmhNAsduwiBNCXb@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Jul 14, 2022 at 07:42:43PM -0400, Bruce Momjian wrote:
> On Wed, Mar 16, 2022 at 09:28:04AM +0100, Laurenz Albe wrote:
> > On Tue, 2022-03-15 at 16:12 +0000, PG Doc comments form wrote:
> > > Page: https://www.postgresql.org/docs/14/backup-dump.html
> > >
> > > As far as I can see, the terms "Reload" and "Restore" are used
> > > interchangeably.
> > > To make the page as easy digestable for the reader as possible, it´s
> > > advisable to stick to exactly one term.
> >
> > That makes sense, particularly since "reload" typically means something
> > else in PostgreSQL. I think "restore" is better.
> >
> > Do you feel like preparing a patch?
>
> I have created the attached patch. The only place I left "reload" was
> when it was used in pg_dump in "To reload an archive file" and similar
> cases. In those cases, restoring a script or file might be
> misinterpreted.
Patch applied back to PG 11. PG 10 had too many conflicts.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2022-07-22 00:24:03 | Correction |
Previous Message | Bruce Momjian | 2022-07-21 18:43:31 | Re: Documentation Suggestion |