Re: [HACKERS] bug in locking an update tuple chain - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] bug in locking an update tuple chain
Date
Msg-id 20170726212745.cfkuvvnndd6janht@alvherre.pgsql
Whole thread Raw
In response to [HACKERS] bug in locking an update tuple chain  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] asynchronous execution
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] asynchronous execution