pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steven Flatt <steven.flatt@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Foreign Key Deadlocking
Date: Wed, 18 Apr 2007 13:47:37 -0400
Message-ID: <5757.1176918457@sss.pgh.pa.us> (raw)
In-Reply-To: <357fa7590704180807j1906d42u1f0f539ac561dc3e@mail.gmail.com>
References: <357fa7590704180807j1906d42u1f0f539ac561dc3e@mail.gmail.com>

"Steven Flatt" <steven.flatt@gmail.com> 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



view thread (8+ messages)  latest in thread

Message-ID: <5757.1176918457@sss.pgh.pa.us>
Permalink:  ../5757.1176918457@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5757.1176918457@sss.pgh.pa.us

 · 

reply

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-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, steven.flatt@gmail.com
  Subject: Re: Foreign Key Deadlocking
  In-Reply-To: <5757.1176918457@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