Re: table-level and row-level locks.

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: table-level and row-level locks.
Date: 2003-08-20 18:45:23
Message-ID: 13694.1061405123@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2003-08-20 18:56:56 Re: Buglist
Previous Message Thomas Swan 2003-08-20 18:35:35 Re: Can't find thread on Linux memory overcommit