BUG #18823: pg_restore not work
The following bug has been logged on the website:
Bug reference: 18823
Logged by: Arslan Aliev
Email address: arslanaliev@yahoo.com
PostgreSQL version: 17.0
Operating system: windows 11
Description:
Hi,
I have done this:
pg_dump --verbose -F c -Z 0 -U *heroku_user* -h *heroku_host* -p 5432
d9jdaocgko2g41 > heroku.dump
Result :
File heroku.dump was created in my local directory with size 1644 KB
Then I create db in my local server
psql -h 'localhost' -p 5434 -U postgres -c "CREATE DATABASE
d9jdaocgko2g41"
Recieved :
Db was created in local server (without tables)
Result : I checked with pgadmin – OK, empty DB was created.
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
I checked local DB with pgadmin – NO tables was created.
Help me, please!!
Regards
Arslan Aliev
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