Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Legacy foreign keys
- 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: Mon, 10 Dec 2007 17:08:12 -0500
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
- Follow-Ups:
- Re: Legacy foreign keys
- From: Peter Koczan
- Re: Legacy foreign keys
- References:
- Legacy foreign keys
- From: Peter Koczan
- Re: Legacy foreign keys
- From: Alvaro Herrera
- Legacy foreign keys
- Prev by Date: Re: Dangerous hint in the PostgreSQL manual
- Next by Date: Re: Case studies
- Previous by thread: Re: Legacy foreign keys
- Next by thread: Re: Legacy foreign keys
- Indexes: