LOCK.tag(figuring out granularity of lock)-- - Mailing list pgsql-general

From Jenny -
Subject LOCK.tag(figuring out granularity of lock)--
Date
Msg-id BAY1-F84oIZP0n4c5Ve0002f273@hotmail.com
Whole thread Raw
List pgsql-general
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.  "


what field in LOCK.tag is tupleId?
thanks
jenny

_________________________________________________________________
MSN 8: Get 6 months for $9.95/month. http://join.msn.com/?page=dept/dialup


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL upgrade -> fails to start server
Next
From: Tom Lane
Date:
Subject: Re: Optimizer isn't perfect