X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 035F18B9E12 for ; Thu, 17 Feb 2005 15:52:38 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47096-03 for ; Thu, 17 Feb 2005 15:52:23 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 97D768BA2CC for ; Thu, 17 Feb 2005 15:52:26 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.1/8.13.1) with ESMTP id j1HFpd5E031017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Feb 2005 08:51:41 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.1/8.13.1) with ESMTP id j1HFpdfE026142; Thu, 17 Feb 2005 08:51:39 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.1/8.13.1/Submit) id j1HFpdNT026141; Thu, 17 Feb 2005 08:51:39 -0700 (MST) (envelope-from mfuhr) Date: Thu, 17 Feb 2005 08:51:38 -0700 From: Michael Fuhr To: Gourish Singbal Cc: PostgreSQL Admin Subject: Re: ERROR: 40P01: Message-ID: <20050217155138.GA26078@winnie.fuhr.org> References: <674d1f8a0502170354692cca73@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <674d1f8a0502170354692cca73@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/158 X-Sequence-Number: 16326 On Thu, Feb 17, 2005 at 05:24:10PM +0530, Gourish Singbal wrote: > I got the below ERROR in my log file. Where can i get more info no > what exactly caused this ERROR and how to debug it?. > > 2005-02-17 02:23:09 ERROR: 40P01: deadlock detected > 2005-02-17 02:23:09 ERROR: 25P02: current transaction is aborted, > commands ignored until end of transaction block Application code must be failing somewhere -- aren't you seeing those problems? Or do the applications not perform enough error checking and reporting? On the server side, if you're running 7.3 or later then you could use log_min_error_statement. See the "Run-time Configuration" section in the "Server Run-time Environment" chapter of the documentation, in particular "Error Reporting and Logging" (or "Logging and Debugging," depending on the version). -- Michael Fuhr http://www.fuhr.org/~mfuhr/