Re: table-level and row-level locks. - Mailing list pgsql-hackers

From Jenny -
Subject Re: table-level and row-level locks.
Date
Msg-id BAY1-F117lHzgVCyiuC00021418@hotmail.com
Whole thread Raw
In response to table-level and row-level locks.  ("Jenny -" <nat_lazy@hotmail.com>)
Responses Re: table-level and row-level locks.  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List 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.  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@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

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



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: [GENERAL] Needed function IF(expr, expr, expr)
Next
From: Rod Taylor
Date:
Subject: Re: [GENERAL] Needed function IF(expr, expr, expr)