Skip site navigation (1) Skip section navigation (2)

"pg_restore -d base" cumstom format broken in CVS head?

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: "pg_restore -d base" cumstom format broken in CVS head?
Date: 2004-08-30 14:49:24
Message-ID: Pine.LNX.4.58.0408301626520.27765@sablons.cri.ensmp.fr (view raw or flat)
Thread:
Lists: pgsql-bugs
Dear bug-hunters,

Sorry if this one was already reported. I don't have access to
http://archives.postgresql.org to check for redundancy, because of a time
out. Is it online?

It seems to me that "pg_restore -d base" is broken in CVS head on my linux
debian box. With a fresh installation the following is ok:

	sh> pg_restore comics.dbz | pgsql comics

although the next one is not:

	sh> pg_restore -d comics comics.dbz

pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC Entry 1542; 0 17234 TABLE DATA a_ecrit coelho
pg_restore: [archiver (db)] could not execute query: ERROR:  relation "a_ecrit" does not exist
    Command was: COPY a_ecrit (auteur, oeuvre) FROM stdin;
pg_restore: [archiver (db)] Error from TOC Entry 1543; 0 17238 TABLE DATA auteurs coelho
pg_restore: [archiver (db)] could not execute query: ERROR:  syntax error at or near "31" at character 1
    Command was: 31     1
5       1
3       1
...

It seems that the internal parsor is desynchronized. File "comics.dbz" was
create just before with a :

	sh> pg_dump --format=c --verbose --compress=9 --file=comics.dbz

but an old (few months) file gives the same result.

the precious "comics.dbz" file is available for tests if you wish at:
http://www.coelho.net/comics.dbz

Have a nice day,

-- 
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-08-30 15:31:12
Subject: Re: Error: could not find a feasible split point for "obs_v_file_id_index"
Previous:From: Martin PittDate: 2004-08-30 13:05:00
Subject: Re: Fwd: Bug#260350: postgresql-dev: libpq3-config output is woeful

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group