Re: BUG #18823: pg_restore not work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: arslanaliev(at)yahoo(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18823: pg_restore not work
Date: 2025-02-22 16:34:47
Message-ID: 3989821.1740242087@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2025-02-22 16:39:52 Re: BUG #18822: mailing lists reject mails due to DKIM-signature
Previous Message PG Bug reporting form 2025-02-22 15:28:16 BUG #18823: pg_restore not work