granularity of locks in postgresql - Mailing list pgsql-hackers

From Jenny -
Subject granularity of locks in postgresql
Date
Msg-id BAY1-F40I8VqzjjKXMH0000b501@hotmail.com
Whole thread Raw
List pgsql-hackers
The following lines are from readme file present in the 
\src\backend\storage\lmgr folder of postgresql

"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."


I dont see any field called tupleId in LockTag..does it have another name?
Also, "(we currently never do this)"--> does this mean that we currently can 
acquire tuplelevel(row level) locks in postgresql?
Thank you
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: Tom Lane
Date:
Subject: Re: SQLSTATEs for warnings
Next
From: Bruce Momjian
Date:
Subject: Re: Regression test failure date.