Re: BUG #13523: Unexplained deadlocks (possible race condition)

From: "Jack Douglas" <jack(at)douglastechnology(dot)co(dot)uk>
To: "'Andres Freund'" <andres(at)anarazel(dot)de>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13523: Unexplained deadlocks (possible race condition)
Date: 2015-07-30 08:56:45
Message-ID: 01ae01d0caa5$a9c774a0$fd565de0$@douglastechnology.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> I am wondering if the deadlock reports would be a bit easier to debug if
we didn't just say "blocked by process 9394", but also in which lockmode
it's held currently.

That would certainly help, something like this would have been a big clue in
this case:

...
relation 65605 of database 12141; blocked by RowExclusiveLock held by
process 9393.
...

is that what you mean?

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jack Douglas 2015-07-30 08:57:11 Re: BUG #13523: Unexplained deadlocks (possible race condition)
Previous Message marko 2015-07-30 08:53:52 BUG #13528: LATERAL vs. correlated scalar subquery