pg_dump and foreign keys troubles

From: "Paolo Negri" <hungrylist(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: pg_dump and foreign keys troubles
Date: 2006-11-07 17:25:21
Message-ID: b242f69c0611070925m55bcd9eai3bc8c059cf389c56@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi

I have a dump of a large DB executed with pg_dump (schema and data together).
The original schema declares some foreign keys constaints.

The problem is in the pg_dump all the foreign keys disappear from the
tables because thay are rendered instead as CREATE CONSTRAINT
TRIGGERS.

My problem is that I have to load the dump (from a 7.3) in a brand new
database (8.1) and then I need to do quite a few changes to the schema
dropping some old foreign constraint and adding some different ones.
Since the new datadabase restored from the dump doesn't know about the
old foreign keys but has just a bunch of constraint trigger, it
becomes really trichy to do this kind of job.

How can I tell to pg_dump to dump the schema with foreign keys
construct instead of creating constraint trigger?
If it's impossible what is the common practice to work arount this problem?

thanks

Paolo

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alexander Burbello 2006-11-07 17:34:36 Use Jobs
Previous Message Jerry Sievers 2006-11-07 16:05:38 Manual sys catalog constraint setup to avoid downtime?