Alvaro Herrera <alvherre@xxxxxxxxxxxxxx> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
