LOCK.tag(figuring out granularity of lock)

From: Sumaira Maqsood Ali <sali(at)purdue(dot)edu>
To: pgsql-patches(at)postgresql(dot)org
Subject: LOCK.tag(figuring out granularity of lock)
Date: 2003-08-24 22:28:20
Message-ID: 3F493C04.3020005@purdue.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

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

is blockId same as tag.objId.blkno? what field in LOCK.tag is tupleId?
thanks
Sumaira

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2003-08-24 23:25:55 small typos
Previous Message Andreas Pflug 2003-08-24 21:35:29 non-blocking libpq under win32