| From: | "Jenny -" <nat_lazy(at)hotmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | LOCK.tag(figuring out granularity of lock)-- |
| Date: | 2003-08-24 23:01:02 |
| Message-ID: | BAY1-F79L83mxMAKytt00006407@hotmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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. "
is blockId same as tag.objId.blkno? what field in LOCK.tag is tupleId?
thanks
jenny
_________________________________________________________________
Get MSN 8 and enjoy automatic e-mail virus protection.
http://join.msn.com/?page=features/virus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bupp Phillips | 2003-08-25 00:19:52 | What is the fastest way to get a resultset |
| Previous Message | Tom Lane | 2003-08-24 22:39:18 | Re: Single-file DBs WAS: Need concrete 'Why Postgres |