| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Andrew Sackville-West <awest(at)janrain(dot)com>, pgsql-bugs <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-12 21:03:58 |
| Message-ID: | CAM3SWZSLfYL-=A_ZcR-n3zaVCdnDak2Mziuf7-WpQfFD4Q22zQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Dec 12, 2014 at 12:52 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Okay, I created a reproducer ... but it doesn't work. I mean, the
> commands are fine: if I execute them manually in four sessions in an
> unpatched server I get a deadlock. But isolationtester doesn't know to
> handle more than one blocked session, so it just hangs when the third
> session blocks after the second one is already blocked. :-(
We need a stress-testing framework. I hacked together one for the ON
CONFLICT UPDATE patch (https://github.com/petergeoghegan/upsert) but
a more comprehensive effort is needed.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-12-12 21:16:56 | Re: regression, deadlock in high frequency single-row UPDATE |
| Previous Message | Alvaro Herrera | 2014-12-12 20:52:54 | Re: regression, deadlock in high frequency single-row UPDATE |