Re: [GENERAL] Confusing deadlock report

2016-03-20 Thread Thomas Kellerer
Albe Laurenz schrieb am 16.03.2016 um 14:38: >>> waits for ShareLock on transaction; blocked by process 24342. Process 24342 waits for ShareLock on transaction 39632974; blocked by process 23912. Process 23912: UPDATE alpha SET some_flag = $1 WHERE (id = $2)

Re: [GENERAL] Confusing deadlock report

2016-03-19 Thread Rakesh Kumar
is there a possibility that there is no index on the FKY column bravo.alpha_id. On Wed, Mar 16, 2016 at 11:09 AM, Albe Laurenz wrote: > Thomas Kellerer wrote: > >> Can you determine what statements were executed in these transactions > before the deadlock? > >> It was

Re: [GENERAL] Confusing deadlock report

2016-03-19 Thread Albe Laurenz
Thomas Kellerer wrote: >>> The error as reported in the Postgres log file is this: >>> >>> 2016-03-12 13:51:29.305 CET [23912]: [1-1] >>> user=arthur,db=prod,app=[unknown] ERROR: deadlock detected >>> 2016-03-12 13:51:29.305 CET [23912]: [2-1] >>> user=arthur,db=prod,app=[unknown] DETAIL:

Re: [GENERAL] Confusing deadlock report

2016-03-19 Thread Thomas Kellerer
Albe Laurenz schrieb am 16.03.2016 um 13:20: >> The error as reported in the Postgres log file is this: >> >> 2016-03-12 13:51:29.305 CET [23912]: [1-1] user=arthur,db=prod,app=[unknown] >> ERROR: deadlock detected >> 2016-03-12 13:51:29.305 CET [23912]: [2-1] user=arthur,db=prod,app=[unknown]

Re: [GENERAL] Confusing deadlock report

2016-03-19 Thread Thomas Kellerer
Tom Lane schrieb am 16.03.2016 um 14:45: >> 2016-03-12 13:51:29.305 CET [23912]: [2-1] user=arthur,db=prod,app=[unknown] >> DETAIL: Process 23912 waits for ShareLock on transaction; blocked by process >> 24342. >> Process 24342 waits for ShareLock on transaction 39632974; blocked >> by

Re: [GENERAL] Confusing deadlock report

2016-03-19 Thread Tom Lane
Thomas Kellerer writes: > 2016-03-12 13:51:29.305 CET [23912]: [2-1] user=arthur,db=prod,app=[unknown] > DETAIL: Process 23912 waits for ShareLock on transaction; blocked by process > 24342. > Process 24342 waits for ShareLock on transaction 39632974; blocked by >

Re: [GENERAL] Confusing deadlock report

2016-03-18 Thread Albe Laurenz
Thomas Kellerer wrote: >> Can you determine what statements were executed in these transactions before >> the deadlock? >> It was probably one of these that took the conflicting lock. > > Unfortunately not. Statement logging is not enabled on that server > (space-constrained). > > And while we

Re: [GENERAL] Confusing deadlock report

2016-03-18 Thread Albe Laurenz
Thomas Kellerer wrote: > we have a strange (at least to me) deadlock situation which does not seem to > fall into the "usual" > deadlock category. > > The error as reported in the Postgres log file is this: > > 2016-03-12 13:51:29.305 CET [23912]: [1-1] user=arthur,db=prod,app=[unknown] >

[GENERAL] Confusing deadlock report

2016-03-16 Thread Thomas Kellerer
Hello, we have a strange (at least to me) deadlock situation which does not seem to fall into the "usual" deadlock category. The error as reported in the Postgres log file is this: 2016-03-12 13:51:29.305 CET [23912]: [1-1] user=arthur,db=prod,app=[unknown] ERROR: deadlock detected