Re: Contention preventing locking - Mailing list pgsql-hackers

From Konstantin Knizhnik
Subject Re: Contention preventing locking
Date
Msg-id 55146c68-0ded-a43b-68d1-b45e328f6cf6@postgrespro.ru
Whole thread Raw
In response to Re: Contention preventing locking  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Contention preventing locking
List pgsql-hackers

On 20.02.2018 14:26, Simon Riggs wrote:
> Try locking the root tid rather than the TID, that is at least unique
> per page for a chain of tuples, just harder to locate.
>
As far as I understand, it is necessary to traverse the whole page to 
locate root tuple, isn't it?
If so, then I expect it to be too expensive operation. Scanning the 
whole page on tuple update seems to be not an acceptable solution.

-- 
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-hackers by date:

Previous
From: Matheus de Oliveira
Date:
Subject: Re: [PATCH] Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT
Next
From: Simon Riggs
Date:
Subject: Re: Contention preventing locking