Actually, my _big_ question is whether the lack of dependency info
coming from 7.2 is going to cause problems in 7.3, i.e. do we make
assumptions that dependency info is there and in cases it isn't, are
there surprises for users, where things worked fine in 7.2. I want to
know if there are cases where we assumed dependency info was there when
in 7.2 we handled the lack of depenency better.
---------------------------------------------------------------------------
Tom Lane wrote:
> "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> > What about this.
> > 1. Implement pg_get_foreignkey_def() or whatever
> > 2. Adjust pg_dump to dump foreign keys using an ALTER statement
> > 3. Back port the above to rel 7_2_2
> > 4. Release a 7.2.2 version and ask that people upgrade to that version and
> > do a dump before they upgrade to 7.3.
>
> The trouble with this is that 7.2.2 would include a lot of rather poorly
> tested code (code that has not even made it to CVS yet) ... and if
> there's a problem in that code, it breaks dump files whether you are an
> early upgrader to 7.3 or not.
>
> I think that's likely to be a hard sell. The most we are likely to get
> is to ask people to use the 7.3 pg_dump to dump their 7.2 server when
> they are about to upgrade to 7.3 --- even that much is a difficult trick
> for RPM users.
>
> The other problem is that given a 7.2 system catalog setup, it's not
> really any easier to reconstruct "this is a foreign key" on the server
> side than it is to do it on the pg_dump side. So if we can figure out
> how to do it at all, we might as well make pg_dump do the work instead
> of insisting on a server update.
>
> regards, tom lane
>
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073
