pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedERROR: 40P01:
4+ messages / 3 participants
[nested] [flat]
* ERROR: 40P01:
@ 2005-02-17 11:54 Gourish Singbal <gourish@gmail.com>
0 siblings, 2 replies; 4+ messages in thread
From: Gourish Singbal @ 2005-02-17 11:54 UTC (permalink / raw)
To: pgsql-admin
Guys,
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
2005-02-17 02:23:09 ERROR: 25P02: current transaction is aborted,
commands ignored until end of transaction block
2005-02-17 02:23:09 ERROR: 25P02: current transaction is aborted,
commands ignored until end of transaction block
Any help is greatly appreciated
--
Best,
Gourish Singbal
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: ERROR: 40P01:
@ 2005-02-17 15:37 Tom Lane <tgl@sss.pgh.pa.us>
parent: Gourish Singbal <gourish@gmail.com>
1 sibling, 0 replies; 4+ messages in thread
From: Tom Lane @ 2005-02-17 15:37 UTC (permalink / raw)
To: Gourish Singbal <gourish@gmail.com>; +Cc: pgsql-admin
Gourish Singbal <gourish@gmail.com> writes:
> 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
You seem to have suppressed the DETAIL part of that message. It should
have reported something like
DETAIL: Process 7205 waits for AccessExclusiveLock on relation 1096910 of database 994178; blocked by process 7199.
Process 7199 waits for AccessExclusiveLock on relation 1100110 of database 994178; blocked by process 7205.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: ERROR: 40P01:
@ 2005-02-17 15:51 Michael Fuhr <mike@fuhr.org>
parent: Gourish Singbal <gourish@gmail.com>
1 sibling, 1 reply; 4+ messages in thread
From: Michael Fuhr @ 2005-02-17 15:51 UTC (permalink / raw)
To: Gourish Singbal <gourish@gmail.com>; +Cc: 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/
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: ERROR: 40P01:
@ 2005-02-21 15:49 Gourish Singbal <gourish@gmail.com>
parent: Michael Fuhr <mike@fuhr.org>
0 siblings, 0 replies; 4+ messages in thread
From: Gourish Singbal @ 2005-02-21 15:49 UTC (permalink / raw)
To: Michael Fuhr <mike@fuhr.org>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2005-02-21 15:49 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-02-17 11:54 ERROR: 40P01: Gourish Singbal <gourish@gmail.com>
2005-02-17 15:37 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-02-17 15:51 ` Michael Fuhr <mike@fuhr.org>
2005-02-21 15:49 ` Gourish Singbal <gourish@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox