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

On 2015-07-28 16:28:23 +0000, jack@douglastechnology.co.uk wrote:
> 2015-07-28 16:46:19 BST ERROR:  deadlock detected
> 2015-07-28 16:46:19 BST DETAIL:  Process 9394 waits for ExclusiveLock on
> relation 65605 of database 12141; blocked by process 9393.
>         Process 9393 waits for ExclusiveLock on relation 65605 of database
> 12141; blocked by process 9394.
>         Process 9394: select f_test('blah')
>         Process 9393: select f_test('blah')
> 2015-07-28 16:46:19 BST HINT:  See server log for query details.
> 2015-07-28 16:46:19 BST CONTEXT:  SQL function "f_test" statement 1
> 2015-07-28 16:46:19 BST STATEMENT:  select f_test('blah')

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.

Greetings,

Andres Freund