granularity of locks in postgresql
От | Jenny - |
---|---|
Тема | granularity of locks in postgresql |
Дата | |
Msg-id | BAY1-F71NgDPex1EglF000075c6@hotmail.com обсуждение исходный текст |
Ответы |
Re: granularity of locks in postgresql
|
Список | 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 _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
В списке pgsql-hackers по дате отправления: