Re: Effects of cascading references in foreign keys - Mailing list pgsql-performance

From Bruno Wolff III
Subject Re: Effects of cascading references in foreign keys
Date
Msg-id 20051029144835.GA21068@wolff.to
Whole thread Raw
In response to Effects of cascading references in foreign keys  (Martin Lesser <ml-pgsql@bettercom.de>)
Responses Re: Effects of cascading references in foreign keys  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Effects of cascading references in foreign keys  ("Thomas F. O'Connell" <tfo@sitening.com>)
List pgsql-performance
On Sat, Oct 29, 2005 at 13:10:31 +0200,
  Martin Lesser <ml-pgsql@bettercom.de> wrote:
> Which effects have UPDATEs on REFERENCEd TABLEs when only columns in the
> referenced table are updated which are not part of the FOREIGN KEY
> constraint?

In 8.1 there is a check to see if the foreign key value has changed and if
not a trigger isn't queued. In the currently released versions any update
will fire triggers.
The check in comment for trigger.c didn't say if this optimization applied
to both referencing and referenced keys or just one of those.
If you need to know more you can look at the code at:
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/
for trigger.c.

pgsql-performance by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Effects of cascading references in foreign keys
Next
From: Bruno Wolff III
Date:
Subject: Re: Effects of cascading references in foreign keys