Re: [WIP] shared row locks - Mailing list pgsql-patches

From Tom Lane
Subject Re: [WIP] shared row locks
Date
Msg-id 18093.1112069885@sss.pgh.pa.us
Whole thread Raw
In response to [WIP] shared row locks  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: [WIP] shared row locks
Re: [WIP] shared row locks
List pgsql-patches
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> 1. To examine a tuple one must first call LockTuple, which grabs a pin
> and lock in the buffer.  The buffer lock is released right away, but the
> pin is kept.

Surely you don't mean that *every* access to a tuple now has to go
through the lock manager :-(.  Have you done any performance testing?

            regards, tom lane

pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: [WIP] shared row locks
Next
From: Alvaro Herrera
Date:
Subject: Re: [WIP] shared row locks