From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Peter Koczan <pjkoczan(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Legacy foreign keys |
Date: | 2007-12-10 22:08:12 |
Message-ID: | 20427.1197324492@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Peter Koczan escribi:
>> I am having a problem with what appear to be legacy foreign keys in
>> some of my databases (probably pre-7.2 days). They won't restore from
>> 8.2 to 8.3, because the '<unnamed>' field in the called function isn't
>> unique when I try to restore more than one of these legacy keys
> 8.3's pg_dump contains smarts to dump these things as normal FKs. Try
> it.
No, pg_dump isn't involved --- the new smarts are inside the server,
in CREATE CONSTRAINT TRIGGER. It sounds like Peter has a case that is
confusing that new code. Could we see a complete example?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Elvis Henríquez | 2007-12-11 03:49:38 | Re: Case studies |
Previous Message | Andrew Sullivan | 2007-12-10 20:47:50 | Re: Dangerous hint in the PostgreSQL manual |