Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: table-level and row-level locks.
Date
Msg-id 13694.1061405123@sss.pgh.pa.us
Whole thread Raw
In response to Re: table-level and row-level locks.  (Koichi Suzuki <suzukikui@nttdata.co.jp>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Thomas Swan
Date:
Subject: Re: Can't find thread on Linux memory overcommit
Next
From: Manfred Koizar
Date:
Subject: Again on index correlation