Re: ERROR: 40P01:

The DETAIL part is:-
DETAIL:  Process 17593 waits for AccessExclusiveLock on relation
1571110842 of database 917916301; blocked by process 17868.

DETAIL:  Process 25284 waits for AccessShareLock on relation
1613149934 of database 917916301; blocked by process 25010.

the deadlock was from the application end. How can we release such locks?.

regards
gourish



On Thu, 17 Feb 2005 08:51:38 -0700, Michael Fuhr <mike@fuhr.org> wrote:
> 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/
>


--
Best,
Gourish Singbal