Re: Foreign key constraint still active after table row removed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Christoph Jaeger" <christoph(dot)jaeger(at)dhl(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Foreign key constraint still active after table row removed
Date: 2003-09-10 16:41:32
Message-ID: 7883.1063212092@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Christoph Jaeger" <christoph(dot)jaeger(at)dhl(dot)com> writes:
> PostgreSQL version (example: PostgreSQL-7.3.4): postgresql 7.1.3

7.1.3 is ancient history, and no it doesn't have defenses against you
changing a column definition that a foreign key linkage refers to.
I'd recommend updating to 7.3.4.

> The table pg_trigger shows three rows, which seem to point to this no
> longer valid constraint, but I do not think it is a good idea to fiddle
> with this unless one really knows how this all works together.

In 7.1, drop the triggers and you're done. AFAIR this would also be
necessary in 7.2. In 7.3 you could have just dropped the columns you
wanted to drop, and not had all these problems.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Theodore Petrosky 2003-09-10 17:39:24 the OS X december update saga....
Previous Message Theodore Petrosky 2003-09-10 16:34:31 Re: help with mac osx 10.2.6