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-F165SHRPqq3ELj000209af@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

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online  
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963



pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: When did we get to be so fast?
Next
From: Gaetano Mendola
Date:
Subject: 7.4beta compile warning