Re: Deadlocks caused by a foreign key constraint - Mailing list pgsql-general

From Decibel!
Subject Re: Deadlocks caused by a foreign key constraint
Date
Msg-id 20070816100940.GA54135@nasby.net
Whole thread Raw
In response to Re: Deadlocks caused by a foreign key constraint  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Thu, Aug 16, 2007 at 01:21:43AM -0400, Tom Lane wrote:
> Decibel! <decibel@decibel.org> writes:
> > But... taking a quick look at RI_FKey_check in backend/utils/adt/
> > ri_triggers.c, I don't see it checking to see if the FK has changed,
> > which seems odd. I would think that if the FK fields haven't changed
> > that there's no need to perform the check.
>
> You looked in the wrong place; see AfterTriggerSaveEvent in
> commands/trigger.c

Ahh, I figured it must be in here somewhere...

I guess it's safe to say that RI triggers get a decent amount of special
treatment in the backend compared to normal triggers.
--
Decibel!, aka Jim Nasby                        decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

Attachment

pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: array for cstring type
Next
From: Rainer Bauer
Date:
Subject: Re: Yet Another COUNT(*)...WHERE...question