From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matt Mello <alien@spaceship.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: "deadlock detected" documentation
Date: Thu, 15 May 2003 13:13:44 -0400
Message-ID: <10286.1053018824@sss.pgh.pa.us> (raw)
In-Reply-To: <3EC3C77A.3010006@spaceship.com>
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>
Matt Mello <alien@spaceship.com> writes:
> I see. One item I forgot to mention ... Both update statements have a
> where clause containing txn.terminalid=38. Txn.terminalid is a foreign
> key column in that table (txn.terminalid->terminal.terminalid). Could
> this be the source of the trouble?
Not per se. The problem depends on which rows get updated and in what
sequence --- the contents of the WHERE clause aren't the issue, except
insofar as they determine the set of rows to be updated.
regards, tom lane
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: tgl@sss.pgh.pa.us, alien@spaceship.com
Subject: Re: "deadlock detected" documentation
In-Reply-To: <10286.1053018824@sss.pgh.pa.us>
* 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