X-Original-To: pgsql-sql@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id EDAD6476326 for ; Wed, 7 May 2003 00:46:58 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 2F237476315 for ; Wed, 7 May 2003 00:46:54 -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 h474kxU6024810; Wed, 7 May 2003 00:46:59 -0400 (EDT) To: Matt Mello Cc: pgsql-sql@postgresql.org Subject: Re: "deadlock detected" documentation In-reply-to: <3EB82DA1.7020809@spaceship.com> References: <3EB82DA1.7020809@spaceship.com> Comments: In-reply-to Matt Mello message dated "Tue, 06 May 2003 16:48:17 -0500" Date: Wed, 07 May 2003 00:46:59 -0400 Message-ID: <24809.1052282819@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-32.5 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES 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/111 X-Sequence-Number: 13276 Matt Mello 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