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

From: Andrew Sackville-West <awest(at)janrain(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, 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-11 21:28:55
Message-ID: 20141211212855.GL22364@andrew-ThinkPad-X230
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Kirkwood 2014-12-11 23:05:31 Re: regression, deadlock in high frequency single-row UPDATE
Previous Message Alvaro Herrera 2014-12-11 20:06:57 Re: BUG #12202: json operator ->>with offset