LOCK.tag(figuring out granularity of lock)

From: "Jenny -" <nat_lazy(at)hotmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: LOCK.tag(figuring out granularity of lock)
Date: 2003-08-08 00:02:31
Message-ID: BAY1-F165SHRPqq3ELj000209af@hotmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:

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

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Babak Badaei 2003-08-08 00:02:59 Under vs inheritance
Previous Message The Hermit Hacker 2003-08-08 00:01:55 Re: When did we get to be so fast?