problem with pg_dump and pg_restore

[Fischer Ulrich]

Hi

I try to move my datas from a postresql 7.3.2 to a postgresql 7.4.1. The
database was dumped with:

pg_dumpall -g GLOBALobjects.sql
pg_dump -s DATABASE > DBschema.sql
pg_dump -Fc DATABASE > DBdata.tar

and rebuilt on the new system with:

createdb DATABASE
psql DATABASE < GLOBALobjects.sql
psql DATABASE < tsearch2.sql
psql DATABASE < DBschema.sql
pg_restore -N -a -v -d DATABASE DBdata.tar

All semms to go well except the restoring. pg_restore prints the
following report:

***@susi179:/tmp> pg_restore -N -a -v -d codasdb codasdbdump-d.tar
pg_restore: connecting to database for restore
pg_restore: executing SEQUENCE SET anschrift_ansid_seq
:
pg_restore: executing SEQUENCE SET dokument_docnum_paper_seq
pg_restore: restoring data for table "linkthemen"
pg_restore: restoring data for table "links"
pg_restore: restoring data for table "anschrift"
pg_restore: restoring data for table "kontakt"
pg_restore: restoring data for table "mitarbeiter"
pg_restore: restoring data for table "kunde"
pg_restore: restoring data for table "kontaktperson"
pg_restore: restoring data for table "versuch"
pg_restore: [archiver (db)] could not execute query: ERROR: insert or
update on table "versuch" violates foreign key constraint "$1"
DETAIL: Key (proid)=(0) is not present in table "projekt".
pg_restore: *** aborted because of error



Why are the tables not restored or better dumped in the correct order?
Is there a solution to solve this problem?

Thanks for any help

Ulrich
--
Ulrich G. Fischer Dipl. Natw. ETH
Center Aerodynamics Ruag Aerospace
P.O. Box 301 CH-6032 Emmen
Tel. [phone] Fax. [phone]
***@aerodynamics.ch www.ruag.com


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ***@postgresql.org

[Grega Bremec]

Post by Fischer Ulrich
Hi
I try to move my datas from a postresql 7.3.2 to a postgresql 7.4.1. The
pg_dumpall -g GLOBALobjects.sql
pg_dump -s DATABASE > DBschema.sql
pg_dump -Fc DATABASE > DBdata.tar

Why the schema/data separation? One important freedom you get when combining
schema and data in the dumps is you can alter it after you imported the data
and thus avoid cyclic dependencies where existance of one foreign key mandates
the existance of another, which refers to the first one.

For now though, try eliminating all constraints from the schema dump and
ALTERing the tables after you imported the data.

Hope this helped,

[Fischer Ulrich]

The schema/data separation is higly recommended in the HowTo of tsearch2.
Thanks for your idea, I'l try it!

Ulrich

Post by Grega Bremec

Post by Fischer Ulrich
Hi
I try to move my datas from a postresql 7.3.2 to a postgresql 7.4.1. The
pg_dumpall -g GLOBALobjects.sql
pg_dump -s DATABASE > DBschema.sql
pg_dump -Fc DATABASE > DBdata.tar

Why the schema/data separation? One important freedom you get when combining
schema and data in the dumps is you can alter it after you imported the data
and thus avoid cyclic dependencies where existance of one foreign key mandates
the existance of another, which refers to the first one.
For now though, try eliminating all constraints from the schema dump and
ALTERing the tables after you imported the data.
Hope this helped,

--
Ulrich G. Fischer Dipl. Natw. ETH
Center Aerodynamics Ruag Aerospace
P.O. Box 301 CH-6032 Emmen
Tel. [phone] Fax. [phone]
***@aerodynamics.ch www.ruag.com


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

[C***@transplace.com]

When I tried to use the 7.3.2 dump, and use 7.4.1 import, I had several
issues- mostly with data. I actually had to dump with the 7.4.1 dumpall
command, upgrade the DB to 7.4.1, and then everything imported correctly.

Hope this helps,
Corey





Grega Bremec
<***@novifor To: Fischer Ulrich <***@aerodynamics.ch>
um.si> cc: pgsql-***@postgresql.org
Sent by: Subject: Re: [ADMIN] problem with pg_dump and pg_restore
pgsql-admin-***@pos
tgresql.org


04/21/2004 08:28 AM






...and on Wed, Apr 21, 2004 at 02:46:54PM +0200, Fischer Ulrich used the

Post by Fischer Ulrich
Hi
I try to move my datas from a postresql 7.3.2 to a postgresql 7.4.1. The
pg_dumpall -g GLOBALobjects.sql
pg_dump -s DATABASE > DBschema.sql
pg_dump -Fc DATABASE > DBdata.tar

Why the schema/data separation? One important freedom you get when
combining
schema and data in the dumps is you can alter it after you imported the
data
and thus avoid cyclic dependencies where existance of one foreign key
mandates
the existance of another, which refers to the first one.

For now though, try eliminating all constraints from the schema dump and
ALTERing the tables after you imported the data.

Hope this helped,
--
Grega Bremec
Senior Administrator
Noviforum Ltd., Software & Media
http://www.noviforum.si/
(See attached file: att4aa3m.dat)

[Anjan Dave]

Corey,

In my case, I have tried using the 7.4.1 pg_dump in 7.2.3, and it was
missing a lot of libraries...did that happen in your case?

I am wondering if it's really possible in the first place.

Thanks,
Anjan


-----Original Message-----
From: ***@transplace.com [mailto:***@transplace.com]
Sent: Wednesday, April 21, 2004 12:06 PM
To: Grega Bremec
Cc: pgsql-***@postgresql.org; pgsql-admin-***@postgresql.org;
Fischer Ulrich
Subject: Re: [ADMIN] problem with pg_dump and pg_restore


When I tried to use the 7.3.2 dump, and use 7.4.1 import, I had several
issues- mostly with data. I actually had to dump with the 7.4.1 dumpall
command, upgrade the DB to 7.4.1, and then everything imported
correctly.

Hope this helps,
Corey






Grega Bremec

<***@novifor To: Fischer
Ulrich <***@aerodynamics.ch>
um.si> cc:
pgsql-***@postgresql.org
Sent by: Subject: Re: [ADMIN]
problem with pg_dump and pg_restore
pgsql-admin-***@pos

tgresql.org





04/21/2004 08:28 AM









...and on Wed, Apr 21, 2004 at 02:46:54PM +0200, Fischer Ulrich used the

Post by Fischer Ulrich
Hi
I try to move my datas from a postresql 7.3.2 to a postgresql 7.4.1.

The

Post by Fischer Ulrich
pg_dumpall -g GLOBALobjects.sql
pg_dump -s DATABASE > DBschema.sql
pg_dump -Fc DATABASE > DBdata.tar

Why the schema/data separation? One important freedom you get when
combining
schema and data in the dumps is you can alter it after you imported the
data
and thus avoid cyclic dependencies where existance of one foreign key
mandates
the existance of another, which refers to the first one.

For now though, try eliminating all constraints from the schema dump and
ALTERing the tables after you imported the data.

Hope this helped,
--
Grega Bremec
Senior Administrator
Noviforum Ltd., Software & Media
http://www.noviforum.si/
(See attached file: att4aa3m.dat)




---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ***@postgresql.org so that your
message can get through to the mailing list cleanly