From: "Jonathan S. Katz" <jkatz@postgresql.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Pg_dumpall
Date: Sun, 8 Apr 2018 13:01:39 -0400
References: <152311295239.31235.6487236091906987117@wrigleys.postgresql.org>
To: sfmconsult@gmail.com,
 pgsql-docs@lists.postgresql.org
In-Reply-To: <152311295239.31235.6487236091906987117@wrigleys.postgresql.org>
Message-Id: <903C7F7F-C143-47A2-8CF3-0EC48E2390B2@postgresql.org>
Precedence: bulk

Hi,

> On Apr 7, 2018, at 10:55 AM, PG Doc comments form =
<noreply@postgresql.org> wrote:
>=20
> The following documentation comment has been logged on the website:
>=20
> Page: https://www.postgresql.org/docs/10/static/backup-dump.html
> Description:
>=20
> "The basic usage of this command is:
>=20
> pg_dumpall > outfile
> The resulting dump can be restored with psql:
>=20
> psql -f infile postgres
> (Actually, you can specify any existing database name to..."
>=20
> Should this not read :
> psql-f outfile postgres

Technically it is correct: you=E2=80=99re dumping data to an output =
file,
and reading the data in from an input file.  The documentation
also makes reference to what the =E2=80=9Coutfile=E2=80=9D and =
=E2=80=9Cinfile=E2=80=9D 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 =E2=80=9Cdumpfile=E2=80=9D would be more clear?

Jonathan