LOCK.tag(figuring out granularity of lock)

From: "Jenny -" <nat_lazy(at)hotmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: LOCK.tag(figuring out granularity of lock)
Date: 2003-08-07 15:08:54
Message-ID: BAY1-F28okSUIwMw8lO00027811@hotmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:

"If we are setting a table level lock
both the blockId and tupleId (in an item pointer this is called
the position) are set to invalid, if it is a page level lock the
blockId is valid, while the tupleId is still invalid. Finally if
this is a tuple level lock (we currently never do this) then both
the blockId and tupleId are set to valid specifications. "

how do we check whether blockId and tupleId of LOCK.tag are valid or
invalid?
is blockId same as tag.objId.blkno? what field in LOCK.tag is tupleId?
thanks
jenny

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-08-07 15:12:05 new psql \d command
Previous Message Larry Rosenman 2003-08-07 14:58:00 Re: 7.4beta1 build problem on unixware