Re: "deadlock detected" documentation

Tom Lane wrote:
> Matt Mello <alien@spaceship.com> writes:
> 
>>The two situations I can think of are:
>>1) Two FK fields in a single row pointing to 2 different FK tables, for 
>>which any 2 updates get locks in opposite order (seems like a deadlock).
> 
> 
> I don't think this is possible, at least in 7.3.  All backends are
> guaranteed to run the triggers of a given table in the same order,
> so the foreign-row locks should be acquired in the same column order
> in all cases.

Except the sessions set deferred modes differently.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #