Re: BUG #18823: pg_restore not work

PG Bug reporting form <noreply@postgresql.org> writes:
> I have done this:

> pg_dump --verbose -F c -Z 0 -U *heroku_user* -h *heroku_host* -p 5432
> d9jdaocgko2g41 > heroku.dump

> pg_restore --verbose --no-acl --no-owner -h 'localhost' -p 5434 -d
> d9jdaocgko2g41 heroku.dump
> Recieved :
> pg_restore: warning: invalid creation date in header
> pg_restore: connecting to database for restore
> pg_restore: implied data-only restore

This looks like the heroku.dump file was corrupted somewhere between
pg_dump and pg_restore.  Did you transport it to a different machine,
and if so how'd you do that exactly?

Also, since you mention using Windows, it might be a good idea to
use "-f heroku.dump" not "> heroku.dump" in the pg_dump call.
I think shell redirection is not too friendly to non-text data
on that platform.

            regards, tom lane