| 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-14 23:42:43 |
| Message-ID: | YtCp8+uNTqszgk1v@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| Attachment | Content-Type | Size |
|---|---|---|
| reload.diff | text/x-diff | 16.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-07-15 01:08:49 | Re: CREATE TABLE AS, section IF NOT EXISTS should clarify what happens to the data |
| Previous Message | Bruce Momjian | 2022-07-14 22:23:43 | Re: Documentation Suggestion |