From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | sfmconsult(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Pg_dumpall |
Date: | 2018-04-08 17:01:39 |
Message-ID: | 903C7F7F-C143-47A2-8CF3-0EC48E2390B2@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Hi,
> On Apr 7, 2018, at 10:55 AM, PG Doc comments form <noreply(at)postgresql(dot)org> wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/backup-dump.html
> Description:
>
> "The basic usage of this command is:
>
> pg_dumpall > outfile
> The resulting dump can be restored with psql:
>
> psql -f infile postgres
> (Actually, you can specify any existing database name to..."
>
> Should this not read :
> psql-f outfile postgres
Technically it is correct: you’re dumping data to an output file,
and reading the data in from an input file. The documentation
also makes reference to what the “outfile” and “infile” represent.
That being said, I can see how it can be confusing particularly
if you are reading through the documentation quickly. Perhaps
a name like “dumpfile” would be more clear?
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-04-08 20:21:54 | Re: Pg_dumpall |
Previous Message | PG Doc comments form | 2018-04-07 14:55:52 | Pg_dumpall |