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
In-reply-to: <18823-e1faa13b1da74705@postgresql.org>
References: <18823-e1faa13b1da74705@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 22 Feb 2025 15:28:16 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3989820.1740242087.1@sss.pgh.pa.us>
Date: Sat, 22 Feb 2025 11:34:47 -0500
Message-ID: <3989821.1740242087@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3989821.1740242087%40sss.pgh.pa.us>
Precedence: bulk

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