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

Alvaro Herrera <alvherre@2ndquadrant.com>

From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Andrew Sackville-West <awest@janrain.com>, pgsql-bugs@postgresql.org, Paulo Tanimoto <paulo@janrain.com>
Date: 2014-12-12T21:57:52Z
Lists: pgsql-bugs

Attachments

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

Commits

  1. Add isolationtester spec for old heapam.c bug

  2. Improve concurrency of foreign key locking