Re: regression, deadlock in high frequency single-row UPDATE

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
Cc: Andrew Sackville-West <awest(at)janrain(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-12 21:57:52
Message-ID: 20141212215752.GF1768@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera wrote:
> Alvaro Herrera wrote:
>
> > I'm going to experiment with that idea and see if it leads to a
> > solution. I tried the other idea yesterday (to keep the HW tuple lock
> > we acquire in heap_lock_tuple until heap_update is done) but aside from
> > being very complicated and bug-prone, it doesn't solve the problem
> > anyway.
>
> Here's a preliminary patch.

Here's a finished version of this patch, which I messed a bit with and
so needs some extra testing. I want to push this shortly and backpatch
to 9.4 and 9.3. I don't want to disrupt the 9.4.0 release next week,
but it'd be nice not to ship it with this bug.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
deadlock-2.patch text/x-diff 11.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message jonlachlan 2014-12-13 22:11:34 BUG #12228: Primary use-case of PERCENT_RANK not supported
Previous Message Peter Geoghegan 2014-12-12 21:31:56 Re: regression, deadlock in high frequency single-row UPDATE