| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | dmigowski(at)ikoffice(dot)de |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6313: Deadlock reporting contains not enought details |
| Date: | 2011-12-01 16:54:28 |
| Message-ID: | 4294.1322758468@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
dmigowski(at)ikoffice(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | d.rericha | 2011-12-01 17:40:24 | BUG #6314: The like command does not handle a long string of special chars |
| Previous Message | dmigowski | 2011-12-01 16:00:46 | BUG #6313: Deadlock reporting contains not enought details |