From: Sumaira Maqsood Ali <sali@purdue.edu>
To: pgsql-docs@postgresql.org
Subject: LOCK.tag(figuring out granularity of lock)
Date: Sun, 24 Aug 2003 17:28:45 -0500
Message-ID: <3F493C1D.3090607@purdue.edu> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: sali@purdue.edu
Subject: Re: LOCK.tag(figuring out granularity of lock)
In-Reply-To: <3F493C1D.3090607@purdue.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox