Re: tablelevel and rowlevel locks - Mailing list pgsql-hackers

From Jenny -
Subject Re: tablelevel and rowlevel locks
Date
Msg-id BAY1-F13314bcLMqvsy00028d1d@hotmail.com
Whole thread Raw
In response to tablelevel and rowlevel locks  ("Jenny -" <nat_lazy@hotmail.com>)
Responses Re: tablelevel and rowlevel locks  (Alvaro Herrera Munoz <alvherre@dcc.uchile.cl>)
List pgsql-hackers
>On Thu, Sep 04, 2003 at 08:56:31AM -0700, Jenny - wrote:
> > I am working on a project that involves displaying locking information
> > about each lock taken, whether it be a row level or  table leve llock.
> > When dealing with struct LOCK (src/include/storage) i have noticed that
> > postgreSQL creates a single LOCK  struct for each table in the  db. Like
>if
> > i acquire 2 seperate row level locks on 2 seperate rows, both these
>locks
> > are represented in the same struct LOCK datastructure.
>
>I think the locks would actually by represented by PROCLOCK structures.
>The LOCK structures are for lockable objects, not for actual locks.
>

Well,from what i understand, PROCLOCK stores the TransactionID and the LOCK
its holding lock on ,so
how would PROCLOCK be holding the 'actual' lock as apposed to the lockable
objects?
thanks!

_________________________________________________________________
Use custom emotions -- try MSN Messenger 6.0!
http://www.msnmessenger-download.com/tracking/reach_emoticon


pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: ANONCVS? Is it being updated correctly?
Next
From: Jon Jensen
Date:
Subject: Re: Win32 native port