[HACKERS] granularity of locks in postgresql

2003-07-28 Thread Jenny -
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

[HACKERS] granularity of locks in postgresql

2003-07-27 Thread Jenny -
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

Re: [HACKERS] granularity of locks in postgresql

2003-07-26 Thread Alvaro Herrera
On Sat, Jul 26, 2003 at 10:59:49AM -0700, Jenny - wrote: > 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 t

[HACKERS] granularity of locks in postgresql

2003-07-26 Thread Jenny -
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