Re: table-level and row-level locks.
От | Jenny - |
---|---|
Тема | Re: table-level and row-level locks. |
Дата | |
Msg-id | BAY1-F74sc2zTqgiRwM0002dbfa@hotmail.com обсуждение исходный текст |
Ответ на | table-level and row-level locks. ("Jenny -" <nat_lazy@hotmail.com>) |
Список | pgsql-hackers |
>A row lock is represented by storing the locking transaction's ID in >xmax and setting the HEAP_MARKED_FOR_UPDATE infomask bit. Where is 'xmax' found? is it at code level or on disk? thanks Jenny >From: Tom Lane <tgl@sss.pgh.pa.us> >To: suzukikui@nttdata.co.jp >CC: pgsql-hackers@postgresql.org >Subject: Re: [HACKERS] table-level and row-level locks. Date: Wed, 20 Aug >2003 14:45:23 -0400 > >Koichi Suzuki <suzukikui@nttdata.co.jp> writes: > > I need to know where such "lock marks" are stored in the source level. > >A row lock is represented by storing the locking transaction's ID in >xmax and setting the HEAP_MARKED_FOR_UPDATE infomask bit. The bit is >needed to distinguish this from the case where the transaction is >deleting the tuple. > > regards, tom lane > >---------------------------(end of broadcast)--------------------------- >TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html _________________________________________________________________ Get MSN 8 and help protect your children with advanced parental controls. http://join.msn.com/?page=features/parental
В списке pgsql-hackers по дате отправления: