X-Original-To: pgsql-sql@postgresql.org
Received: from spampd.localdomain (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id D4CD4475956
	for <pgsql-sql@postgresql.org>; Tue,  6 May 2003 17:48:33 -0400 (EDT)
Received: from ms-smtp-01.texas.rr.com (ms-smtp-01.texas.rr.com
 [24.93.36.229])
	by postgresql.org (Postfix) with ESMTP id 103F3474E42
	for <pgsql-sql@postgresql.org>; Tue,  6 May 2003 17:48:33 -0400 (EDT)
Received: from spaceship.com (cs24243211-128.austin.rr.com [24.243.211.128])
	by ms-smtp-01.texas.rr.com (8.12.5/8.12.2) with ESMTP id h46LmY8b024458
	for <pgsql-sql@postgresql.org>; Tue, 6 May 2003 16:48:34 -0500 (CDT)
Message-ID: <3EB82DA1.7020809@spaceship.com>
Date: Tue, 06 May 2003 16:48:17 -0500
From: Matt Mello <alien@spaceship.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: "deadlock detected" documentation
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No,
 hits=-12.9 required=5.0 tests=BAYES_01,USER_AGENT_MOZILLA_UA
	autolearn=ham	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Archive-Number: 200305/108
X-Sequence-Number: 13273

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.]

TIA!

-- 
Matt Mello