| 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 19:15:07 |
| Message-ID: | BAY1-F129wP6SAH2JZZ0000671c@hotmail.com |
| Views: | Whole Thread | Raw Message | 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
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-08 19:21:42 | Re: consistency check on SPI tuple count failed |
| Previous Message | Larry Rosenman | 2003-08-08 19:12:39 | Re: build on unixware 713 |