Re: Reconstructing FKs in pg_dump

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reconstructing FKs in pg_dump
Date: 2002-09-26 21:12:09
Message-ID: 1033074730.26731.274.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2002-09-26 at 16:57, Tom Lane wrote:
> This means that RI trigger definitions dating back to 7.0 (or whenever
> it was that we fixed the pg_dump bug about not dumping tgconstrrelid)
> don't work anymore.

I thought 7.0 introduced foreign keys in the first place, so perhaps
7.1?

However, if they're coming from 7.0 or earlier would it be appropriate
to have them bounce through 7.2 / 7.1 first?

Pain in the ass to dump and reload twice to get to the latest, but since
they only upgrade once every 2 to 3 years...

Is this the only problem that 7.0 people are going to experience (server
side, SQL changes are abundant)?

> 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.

If this type of stuff has to be done, then this is probably the best way
to go.

--
Rod Taylor

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2002-09-26 21:15:05 Re: Reconstructing FKs in pg_dump
Previous Message Greg Copeland 2002-09-26 21:09:15 Re: [HACKERS] Performance while loading data and indexing