Re: regression, deadlock in high frequency single-row UPDATE - Mailing list pgsql-bugs

From Andrew Sackville-West
Subject Re: regression, deadlock in high frequency single-row UPDATE
Date
Msg-id 20141211212855.GL22364@andrew-ThinkPad-X230
Whole thread Raw
In response to Re: regression, deadlock in high frequency single-row UPDATE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
On Thu, Dec 11, 2014 at 02:22:56PM -0300, 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.

We can try that. We don't currently build our own pg, so it'll take a
bit for us to get there. I'll report back with results.

A

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #12202: json operator ->>with offset
Next
From: Mark Kirkwood
Date:
Subject: Re: regression, deadlock in high frequency single-row UPDATE