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: Wed, 07 May 2003 00:46:59 -0400
Message-ID: <24809.1052282819@sss.pgh.pa.us> (raw)
In-Reply-To: <3EB82DA1.7020809@spaceship.com>
References: <3EB82DA1.7020809@spaceship.com>
Matt Mello <alien@spaceship.com> writes:
> I just got a "deadlock detected" SQL error from the backend. I've never
> received one of these before, but I just released new pooling code, so
> I'm concerned.
> Can someone point me to documentation on what this is and how to prevent
> it? [My search on the newsgroups yielded far too much for me to read.]
It means user A is waiting for a lock held by user B, while user B
is waiting for a lock held by user A. For better info you'll need
to offer more details about what your applications are doing ...
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: <24809.1052282819@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