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-26T16:56:07Z
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.  It does solve the deadlock in my simplified
> test case.  If Andrew can confirm that it fixes his original problem
> too, that'd be good.

Pushed this patch to master, 9.4 and 9.3.

-- 
Á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