From: Tom Lane <tgl@sss.pgh.pa.us>
To: arslanaliev@yahoo.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18823: pg_restore not work
Date: Sat, 22 Feb 2025 11:34:47 -0500
Message-ID: <3989821.1740242087@sss.pgh.pa.us> (raw)
In-Reply-To: <18823-e1faa13b1da74705@postgresql.org>
References: <18823-e1faa13b1da74705@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, arslanaliev@yahoo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18823: pg_restore not work
In-Reply-To: <3989821.1740242087@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox