Re: BUG #6313: Deadlock reporting contains not enought details - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6313: Deadlock reporting contains not enought details
Date
Msg-id 4294.1322758468@sss.pgh.pa.us
Whole thread Raw
In response to BUG #6313: Deadlock reporting contains not enought details  (dmigowski@ikoffice.de)
List pgsql-bugs
dmigowski@ikoffice.de writes:
> PostgreSQL version: 8.3.16

> In my application I receive deadlocks from time to time, reported by an
> error message like this:

> ERROR: deadlock detected
> SQL Status:40P01
> Detail:Process 30812 waits for ShareLock on transaction 278158200; blocked
> by process 2852.
> Process 2852 waits for ShareLock on transaction 278158159; blocked by
> process 30812.

> This is absolutely useless for me for the following reasons.

If you were running a more modern version of Postgres, you would find a
more complete report about the deadlock in the postmaster log.  We're
not going to change it in 8.3.x though.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Suneel Kumar M
Date:
Subject: Postgre Cross compilation for coldfire processor.
Next
From: d.rericha@healthcareoss.com
Date:
Subject: BUG #6314: The like command does not handle a long string of special chars