Re: Reconstructing FKs in pg_dump - Mailing list pgsql-hackers

From Matthew T. O'Connor
Subject Re: Reconstructing FKs in pg_dump
Date
Msg-id 008b01c2669b$9d369800$0a00a8c0@zeut2k
Whole thread Raw
In response to Reconstructing FKs in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Reconstructing FKs in pg_dump  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
From: "Tom Lane" <tgl@sss.pgh.pa.us>
> However, if we are going to put that kind of knowledge into pg_dump,
> it would only be a small further step to have it dump these triggers
> as ALTER TABLE ADD CONSTRAINT commands instead.  Which would be a lot
> better for forward compatibility than dumping the raw triggers.

There was some talk of adding Rod Taylor's identifies upgrade script to
contrib, or mentioning it in the release.  I think that it upgrades Foreign
key, Unique, and Serial constraints, is that relevant here?  Could it be
used (or modified) to handle this situation?  Just a thought.


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Cause of missing pg_clog files
Next
From: Alvaro Herrera
Date:
Subject: version mismatch detection doesn't work