Re: table-level and row-level locks.

if table and page are locked in src/backend/storage/lmgr/lmgr.c by
LockRelation() and LockPage respectively, in which file and by which
function is a row locked?
thanks
Jenny

>From: "Jenny -" <nat_lazy(at)hotmail(dot)com>
>To: pgsql-hackers(at)postgresql(dot)org
>Subject: Re: [HACKERS] table-level and row-level locks.
>Date: Sun, 24 Aug 2003 11:30:41 -0700
>
>>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(at)sss(dot)pgh(dot)pa(dot)us>
>>To: suzukikui(at)nttdata(dot)co(dot)jp
>>CC: pgsql-hackers(at)postgresql(dot)org
>>Subject: Re: [HACKERS] table-level and row-level locks. Date: Wed, 20 Aug
>>2003 14:45:23 -0400
>>
>>Koichi Suzuki <suzukikui(at)nttdata(dot)co(dot)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
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend

_________________________________________________________________
MSN 8: Get 6 months for $9.95/month. http://join.msn.com/?page=dept/dialup