Can you please help me solve the problem of ERROR deadlock detected
This is the log incurred in postgressql.log
2009-01-21 15:47:20 IST NOTICE: truncate cascades to table "displet"
2009-01-21 15:47:20 IST NOTICE: truncate cascades to table
"screenscrapesource"
2009-01-21 15:47:20 IST NOTIC
ITAGAKI Takahiro wrote:
> There are some open issues. One of the issues is that the killed query is
> logged by log_min_error_statement, but conflicted query is logged in DETAIL.
> Killed query is logged only on server but conflicted queries are
> sent to both server and client. In addition, if lo
ITAGAKI Takahiro wrote:
> I wrote a small patch to log conflicted queries.
> With my patch, deadlock message will change as following:
>
> | ERROR: deadlock detected
> | DETAIL: Process 3468 waits for ShareLock on transaction 451; blocked by
> process 4068.
> | STATEMENT: UPDATE test S
Hello,
We see error logs something like following on deadlocks:
| ERROR: deadlock detected
| DETAIL: Process 1612 waits for ShareLock on transaction 407; blocked by
process 3388.
| Process 3388 waits for ShareLock on transaction 406; blocked by
process 1612.
| STATEMENT: UPDATE test
