| From: | "Jenny -" <nat_lazy(at)hotmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | granularity of locks in postgresql |
| Date: | 2003-07-28 16:58:05 |
| Message-ID: | BAY1-F40I8VqzjjKXMH0000b501@hotmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The following lines are from readme file present in the
\src\backend\storage\lmgr folder of postgresql
"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."
I dont see any field called tupleId in LockTag..does it have another name?
Also, "(we currently never do this)"--> does this mean that we currently can
acquire tuplelevel(row level) locks in postgresql?
Thank you
Jenny
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2003-07-28 16:58:42 | Re: best way to determine start of new statement within |
| Previous Message | Bruce Momjian | 2003-07-28 16:22:05 | Re: [HACKERS] allowed user/db variables |