From: Jan Wieck <JanWieck@Yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matt Mello <alien@spaceship.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: "deadlock detected" documentation
Date: Mon, 19 May 2003 15:19:27 -0400
Message-ID: <3EC92E3F.6080703@Yahoo.com> (raw)
References: <3EB82DA1.7020809@spaceship.com>
<24809.1052282819@sss.pgh.pa.us>
<3EC32935.5040005@spaceship.com>
<7737.1053003625@sss.pgh.pa.us>
<3EC3C239.7070708@spaceship.com>
<10096.1053017383@sss.pgh.pa.us>
<3EC3C77A.3010006@spaceship.com>
<10286.1053018824@sss.pgh.pa.us>
<3EC3E53C.9070800@spaceship.com>
<3EC50CEB.9080202@spaceship.com>
<28936.1053112428@sss.pgh.pa.us>
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 #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: JanWieck@Yahoo.com, tgl@sss.pgh.pa.us, alien@spaceship.com
Subject: Re: "deadlock detected" documentation
In-Reply-To: <3EC92E3F.6080703@Yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox