Bug in pg_dump/restore -o - Mailing list pgsql-hackers

From Bruce Momjian
Subject Bug in pg_dump/restore -o
Date
Msg-id 200201171749.g0HHnTI13126@candle.pha.pa.us
Whole thread Raw
Responses Re: Bug in pg_dump/restore -o  (Brent Verner <brent@rcfile.org>)
List 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       $
createdbtest       $ 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@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [ADMIN] CREATE OR REPLACE VIEW / TRIGGER
Next
From: Jan Wieck
Date:
Subject: Re: tuptoaster.c must *not* use SnapshotAny