On 11/12/18 11:39 AM, David wrote:
> I'm not following your question. The pre-data and post-data sections
> each go to an individual file, but the data section goes to a
> directory. I can restore the files using psql, but it is the restore of
> the directory that is hanging.
That is not what you showed in your OP:
This pg_dump command works:
pg_dump -U postgres -f predata.sql -F p -v -d prod_data
But a matching pg_restore command does nothing.
pg_restore -U postgres -f predata.sql -v
We would need to see the commands for data section to be able to comment
further.
>
> On Mon, Nov 12, 2018 at 2:28 PM Rob Sargent <robjsargent@gmail.com
> <mailto:robjsargent@gmail.com>> wrote:
>
>
> On 11/12/18 11:44 AM, Tom Lane wrote:
> > David <dlbarron28@gmail.com <mailto:dlbarron28@gmail.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
> >
>
> In this case, does the "General options" -f make sense? restoring to
> a file?
>
>
--
Adrian Klaverfile:///usr/share/applications/thunderbird.desktop
adrian.klaver@aklaver.com