X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D9BCE4768B6 for ; Thu, 15 May 2003 14:41:06 -0400 (EDT) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with ESMTP id 70344-06 for ; Thu, 15 May 2003 14:40:35 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id EABDC4767D1 for ; Thu, 15 May 2003 13:13:44 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h4FHDiU6010287; Thu, 15 May 2003 13:13:44 -0400 (EDT) To: Matt Mello Cc: pgsql-sql@postgresql.org Subject: Re: "deadlock detected" documentation 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> Comments: In-reply-to Matt Mello message dated "Thu, 15 May 2003 11:59:38 -0500" Date: Thu, 15 May 2003 13:13:44 -0400 Message-ID: <10286.1053018824@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/331 X-Sequence-Number: 13496 Matt Mello 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