Re: Contention preventing locking

From: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Contention preventing locking
Date: 2018-02-20 16:07:53
Message-ID: 55146c68-0ded-a43b-68d1-b45e328f6cf6@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2018-02-20 16:39:48 Re: Contention preventing locking
Previous Message Matheus de Oliveira 2018-02-20 16:01:26 Re: [PATCH] Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT