From: | "Jenny -" <nat_lazy(at)hotmail(dot)com> |
---|---|
To: | alvherre(at)dcc(dot)uchile(dot)cl |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] tablelevel and rowlevel locks |
Date: | 2003-09-04 18:21:05 |
Message-ID: | BAY1-F13314bcLMqvsy00028d1d@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general 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
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2003-09-04 18:21:38 | Re: automatic update |
Previous Message | Richard Huxton | 2003-09-04 18:18:20 | Re: Crosstab function Problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-09-04 18:25:33 | Re: Win32 native port |
Previous Message | Doug McNaught | 2003-09-04 18:20:53 | Re: Win32 native port |