Re: Pg_dumpall

2018-04-09 Thread Steve M
Thank you for responding. *Best regards,* *Steve Maio* On Sun, Apr 8, 2018 at 4:21 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: > >> On Apr 7, 2018, at 10:55 AM, PG Doc comments form < > nore...@postgresql.org> wrote: > >> Should this not read : > >> psql-f outfile postgres > > > Technic

Re: Pg_dumpall

2018-04-08 Thread Tom Lane
"Jonathan S. Katz" writes: >> On Apr 7, 2018, at 10:55 AM, PG Doc comments form >> wrote: >> 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 refere

Re: Pg_dumpall

2018-04-08 Thread Jonathan S. Katz
Hi, > On Apr 7, 2018, at 10:55 AM, PG Doc comments form > 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 comma

Pg_dumpall

2018-04-07 Thread PG Doc comments form
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,

pg_dumpall examples may lead to encoding problems

2017-12-27 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/app-pg-dumpall.html Description: The example to dumb all databases at the bottom of the page "pg_dumpall > db.out" works, but I think it would be better to suggest &q