| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org, Paulo Tanimoto <paulo(at)janrain(dot)com> |
| Subject: | Re: regression, deadlock in high frequency single-row UPDATE |
| Date: | 2014-12-09 05:58:58 |
| Message-ID: | 54868FA2.80003@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 09/12/14 12:55, Andrew Sackville-West wrote:
> Some months later (stupid business priorities...) we have something to
> report on this. We have been able to produce a minimal schema to
> demonstrate the problem, and successfully induced the deadlock using
> pgbench (thanks to Paulo Tanimoto, cc-ed here).
>
> Please see:
>
> https://gist.github.com/andrewsw-janrain/40d1687db013b1e7c3b3
>
> for detailed instructions on how to trigger the deadlock.
>
> I would be thrilled to learn that we've done something wrong here,
> otherwise I think this represents a regression introduced in 9.3.
>
>
That is interesting - FWIW I can reproduce:
- 9.2.9 no deadlock
- 9.4rc1 many deadlocks
so something has changed after 9.2 for sure!
Just mucking about I changed certain things in your schema setup
(removed ON DELETE CASCADE, use CURRENT_TIMESTAMP instead of
now()...lessen the use of DEFAULT)...however still seeing deadlocks in
9.4, so at least it is easy to reproduce!
Regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitri Koulikov | 2014-12-09 11:08:39 | Re: BUG #12137: ORDER BY with expresion changes the output if added |
| Previous Message | Andrew Sackville-West | 2014-12-08 23:55:52 | Re: regression, deadlock in high frequency single-row UPDATE |