Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id D36BF9FB558 for ; Wed, 18 Apr 2007 14:47:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 97208-01 for ; Wed, 18 Apr 2007 14:47:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 827489FB6E8 for ; Wed, 18 Apr 2007 14:47:39 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l3IHlbL0005758; Wed, 18 Apr 2007 13:47:38 -0400 (EDT) To: "Steven Flatt" cc: pgsql-performance@postgresql.org Subject: Re: Foreign Key Deadlocking In-reply-to: <357fa7590704180807j1906d42u1f0f539ac561dc3e@mail.gmail.com> References: <357fa7590704180807j1906d42u1f0f539ac561dc3e@mail.gmail.com> Comments: In-reply-to "Steven Flatt" message dated "Wed, 18 Apr 2007 11:07:08 -0400" Date: Wed, 18 Apr 2007 13:47:37 -0400 Message-ID: <5757.1176918457@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/335 X-Sequence-Number: 24212 "Steven Flatt" writes: > Hi, we're using Postgres 8.1.4. > We've been seeing deadlock errors of this form, sometimes as often as > several times per hour: > ... > I also see claims that this problem is fixed in 8.2, and if the fix is what > I think it is, it's also in 8.1.6. > Can someone confirm that I've identified the right fix? Hard to say without a lot more data, but as a general rule you should be on 8.1.latest in any case. See http://www.postgresql.org/support/versioning You might also find ammunition in the release notes: http://developer.postgresql.org/pgdocs/postgres/release.html regards, tom lane