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-25 14:45:52 |
Message-ID: | BAY1-F90bzpTtncIixr00008035@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. "
is blockId same as tag.objId.blkno? what field in LOCK.tag is tupleId?
thanks
jenny
_________________________________________________________________
Get MSN 8 and help protect your children with advanced parental controls.
http://join.msn.com/?page=features/parental
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-08-25 15:23:51 | Re: I am back |
Previous Message | Gavin Sherry | 2003-08-25 06:50:15 | Re: I am back |