Bug in pg_dump/restore -o

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Bug in pg_dump/restore -o
Date: 2002-01-17 17:49:29
Message-ID: 200201171749.g0HHnTI13126@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I am seeing a bug in CVS in pg_dump/pg_restore with -o:

$ dropdb test
$ createdb test
$ pg_dump -Fc -b -o test > /bjm/out
$ dropdb test
$ createdb test
$ pg_restore -v -d test /bjm/out
pg_restore: connecting to database for restore
pg_restore: creating <Init> Max OID
pg_restore: [archiver (db)] could not execute query: no result from server
pg_restore: *** aborted because of error

It fails even on an empty database. It appears to be the setting of the
max oid:

CREATE TEMPORARY TABLE pgdump_oid (dummy int4);
COPY pgdump_oid WITH OIDS FROM stdin;
16612 0
\.
DROP TABLE pgdump_oid;

It seems the -Fc format is somehow misinterpreting this. I am
researching this now but if someone has a clue, I could use it.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2002-01-17 18:11:24 Re: tuptoaster.c must *not* use SnapshotAny
Previous Message Tom Lane 2002-01-17 15:33:24 Re: [ADMIN] CREATE OR REPLACE VIEW / TRIGGER