Skip site navigation (1) Skip section navigation (2)

Re: [WIP] shared row locks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [WIP] shared row locks
Date: 2005-03-29 04:18:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)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

In response to


pgsql-patches by date

Next:From: Alvaro HerreraDate: 2005-03-29 04:36:22
Subject: Re: [WIP] shared row locks
Previous:From: Robert CreagerDate: 2005-03-29 04:15:43
Subject: Re: BUG #1563: wrong week returnded by date_trunc('week',

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group