| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | jack(at)douglastechnology(dot)co(dot)uk, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #13523: Unexplained deadlocks (possible race condition) |
| Date: | 2015-07-29 11:13:26 |
| Message-ID: | 20150729111326.GD24218@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2015-07-28 16:28:23 +0000, jack(at)douglastechnology(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kumarsathishms | 2015-07-29 12:13:50 | BUG #13525: Database crashed with several error messages "Could not open file "pg_multixact/members/" |
| Previous Message | Peter J. Holzer | 2015-07-29 09:41:20 | Re: Segfault in pg_stat_activity |