| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(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:16:56 |
| Message-ID: | 20141212211656.GD1768@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Peter Geoghegan wrote:
> 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.
Hm, that's nice, but I hope you realize that a framework based on shell
scripts cannot possibly work for us.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-12-12 21:31:56 | Re: regression, deadlock in high frequency single-row UPDATE |
| Previous Message | Peter Geoghegan | 2014-12-12 21:03:58 | Re: regression, deadlock in high frequency single-row UPDATE |