Re: table-level and row-level locks.

>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.

where is 'HEAP_MARKED_FOR_UPDATE infomask bit' found ?
thanks

>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

_________________________________________________________________
Use custom emotions -- try MSN Messenger 6.0!
http://www.msnmessenger-download.com/tracking/reach_emoticon