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-F7PqngL6wxvw0I0002146d@hotmail.com
Whole thread Raw
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

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail



pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Release changes
Next
From: Tom Lane
Date:
Subject: Re: logging stuff