locking granularity

From: "Jenny -" <nat_lazy(at)hotmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: locking granularity
Date: 2003-08-02 21:27:51
Message-ID: BAY1-F37XeYg6E64wzV0000dc9a@hotmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2003-08-02 21:39:24 Re: Identification of serial fields
Previous Message Andrew Dunstan 2003-08-02 21:24:56 logging dbname