Skip site navigation (1) Skip section navigation (2)

Re: ERROR: 40P01:

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Gourish Singbal <gourish(at)gmail(dot)com>
Cc: PostgreSQL Admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: ERROR: 40P01:
Date: 2005-02-17 15:51:38
Message-ID: 20050217155138.GA26078@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-admin
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/

In response to

Responses

pgsql-admin by date

Next:From: InsydeDate: 2005-02-17 19:39:24
Subject: ODBC driver version
Previous:From: Tom LaneDate: 2005-02-17 15:37:16
Subject: Re: ERROR: 40P01:

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group