Re: BUG #5505: Busted referential integrity with triggers - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5505: Busted referential integrity with triggers
Date
Msg-id 12336.1276524821@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5505: Busted referential integrity with triggers  ("Tommy McDaniel" <tommstein@myway.com>)
List pgsql-bugs
"Tommy McDaniel" <tommstein@myway.com> writes:
> Let us also create a trigger to disable UPDATEs on table_2:
> ...
> And, we have now broken referential integrity.

Yup, this is not a bug, it's a feature.  Triggers fire on
referential-integrity updates.  (If they didn't, you could not for
example have a logging trigger log RI actions.)  If you don't want
to break RI, you'd better think more carefully about what your
trigger does.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Shinji Nakajima"
Date:
Subject: BUG #5507: missing chunk number 0 for toast value XXXXX in pg_toast_XXXXX
Next
From: Tom Lane
Date:
Subject: Re: BUG #5506: Error in the grammar of de joins