Re: [HACKERS] tablelevel and rowlevel locks

From: Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl>
To: Jenny - <nat_lazy(at)hotmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] tablelevel and rowlevel locks
Date: 2003-09-04 16:10:16
Message-ID: 20030904161016.GA15428@dcc.uchile.cl
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.

--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Vivir y dejar de vivir son soluciones imaginarias.
La existencia est en otra parte" (Andre Breton)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew L. Gould 2003-09-04 16:15:53 FYI: Avoiding write conflict errors in MS Access clients
Previous Message Csaba Nagy 2003-09-04 16:10:10 Re: Replaceing records

Browse pgsql-hackers by date

  From Date Subject
Next Message Kaare Rasmussen 2003-09-04 16:11:21 Re: FE/BE Protocol - Specific version
Previous Message Greg Stark 2003-09-04 15:57:26 Re: Seqscan in MAX(index_column)