From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | raf <raf(at)raf(dot)org>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Is pg_restore in 10.6 working? |
Date: | 2018-11-12 22:12:33 |
Message-ID: | cbcfd4f9-7c84-7deb-0a28-7117e54ccc93@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/12/18 2:07 PM, raf wrote:
> Tom Lane wrote:
>
>> David <dlbarron28(at)gmail(dot)com> writes:
>>> I have some experience with different versions of Postgres, but I'm just
>>> getting around to using pg_restore, and it's not working for me at all.
>>> ...
>>> But a matching pg_restore command does nothing.
>>> pg_restore -U postgres -f predata.sql -v
>>
>> This command expects to read from stdin and write to predata.sql, so
>> it's not surprising that it's just sitting there. What you want
>> is something along the lines of
>>
>> pg_restore -U postgres -d dbname -v <predata.sql
>>
>> regards, tom lane
>
> Does that mean there's a bug in the usage message?
>
> pg_restore --help says (admittedly on 9.5 but it's probably the same with 10.6):
>
> Usage:
> pg_restore [OPTION]... [FILE]
>
> ...
>
> If no input file name is supplied, then standard input is used.
>
> To me, that says that a filename on the command line after the options
> will be read as the source of the restore. Only if it is absent would
> stdin be used.
The example Tom showed was for using a plain text file as the source
instead of the default which is one of the custom formats.
>
> Apologies if the usage message for 10.6 doesn't say the same thing.
>
> cheers,
> raf
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Om Prakash Jaiswal | 2018-11-13 09:12:36 | Db restore Error literal carriage return found hint use \r |
Previous Message | David | 2018-11-12 22:11:55 | Re: Is pg_restore in 10.6 working? |