Re: table-level and row-level locks.

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Jenny - <nat_lazy(at)hotmail(dot)com>
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, suzukikui(at)nttdata(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org
Subject: Re: table-level and row-level locks.
Date: 2003-09-07 23:52:39
Message-ID: 20030907235239.GA3797@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 07, 2003 at 04:07:42PM -0700, Jenny - wrote:
> >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 ?

Have you ever heard of the "grep" *nix utility? It's quite useful.

Anyway, t_infomask is part of a struct called HeapTupleHeaderData,
defined somewhere in src/include/access/htup.h

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
You liked Linux a lot when he was just the gawky kid from down the block
mowing your lawn or shoveling the snow. But now that he wants to date
your daughter, you're not so sure he measures up. (Larry Greenemeier)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-09-08 00:38:05 Re: Needed function IF(expr, expr, expr)
Previous Message Rod Taylor 2003-09-07 23:25:30 Re: Needed function IF(expr, expr, expr)