pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18823: pg_restore not work
2+ messages / 2 participants
[nested] [flat]

* BUG #18823: pg_restore not work
@ 2025-02-22 15:28 PG Bug reporting form <noreply@postgresql.org>
  2025-02-22 16:34 ` Re: BUG #18823: pg_restore not work Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: PG Bug reporting form @ 2025-02-22 15:28 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: arslanaliev@yahoo.com

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



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: BUG #18823: pg_restore not work
  2025-02-22 15:28 BUG #18823: pg_restore not work PG Bug reporting form <noreply@postgresql.org>
@ 2025-02-22 16:34 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2025-02-22 16:34 UTC (permalink / raw)
  To: arslanaliev@yahoo.com; +Cc: pgsql-bugs@lists.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





^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2025-02-22 16:34 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-22 15:28 BUG #18823: pg_restore not work PG Bug reporting form <noreply@postgresql.org>
2025-02-22 16:34 ` Tom Lane <tgl@sss.pgh.pa.us>

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