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

From Tom Lane
Subject Re: Deadlocks caused by a foreign key constraint
Date
Msg-id 17489.1187241703@sss.pgh.pa.us
Whole thread Raw
In response to Re: Deadlocks caused by a foreign key constraint  (Decibel! <decibel@decibel.org>)
Responses Re: Deadlocks caused by a foreign key constraint  (Decibel! <decibel@decibel.org>)
List pgsql-general
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

            regards, tom lane

pgsql-general by date:

Previous
From: Rodrigo De León
Date:
Subject: Re: Fastest way to import only ONE column into a table? (COPY doesn't work)
Next
From: Tom Lane
Date:
Subject: Re: User-Friendly TimeZone List