LOCK.tag(figuring out granularity of lock) - Mailing list pgsql-hackers

From Jenny -
Subject LOCK.tag(figuring out granularity of lock)
Date
Msg-id BAY1-F129wP6SAH2JZZ0000671c@hotmail.com
Whole thread Raw
Responses Re: LOCK.tag(figuring out granularity of lock)
List pgsql-hackers
following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:

"If we are setting a table level lockboth the blockId and tupleId (in an item pointer this is calledthe position) are
setto invalid, if it is a page level lock theblockId is valid, while the tupleId is still invalid.  Finally ifthis is a
tuplelevel lock (we currently never do this) then boththe 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

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: consistency check on SPI tuple count failed
Next
From: Larry Rosenman
Date:
Subject: Re: build on unixware 713