Re: bug in locking an update tuple chain

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: bug in locking an update tuple chain
Date: 2017-07-26 21:27:45
Message-ID: 20170726212745.cfkuvvnndd6janht@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The attached patch fixes the problem. When locking some old tuple version of
> the chain, if we detect that we already hold that lock
> (test_lockmode_for_conflict returns HeapTupleSelfUpdated), do not try to lock
> it again but instead skip ahead to the next version. This fixes the synthetic
> case in my isolationtester as well as our customer's production case.

Pushed.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-07-26 21:43:49 Re: asynchronous execution
Previous Message Robert Haas 2017-07-26 21:16:43 Re: asynchronous execution