Re: Your application

See the attached file for details
>From pgsql-hackers-owner(at)postgresql(dot)org Wed Aug 20 03:56:14 2003
X-Original-To: pgsql-hackers-postgresql(dot)org(at)localhost(dot)postgresql(dot)org
Received: from localhost (unknown [64.117.224.130])
by svr1.postgresql.org (Postfix) with ESMTP id 9028CD1D139
for <pgsql-hackers-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>; Wed, 20 Aug 2003 03:56:13 -0300 (ADT)
Received: from svr1.postgresql.org ([64.117.224.193])
by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024)
with ESMTP id 45635-02
for <pgsql-hackers-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>;
Wed, 20 Aug 2003 03:56:03 -0300 (ADT)
Received: from ms0.nttdata.co.jp (ms0.nttdata.co.jp [163.135.193.231])
by svr1.postgresql.org (Postfix) with ESMTP id 723FAD1D1F5
for <pgsql-hackers(at)postgresql(dot)org>; Wed, 20 Aug 2003 03:56:00 -0300 (ADT)
Received: from mail0.nttdata.co.jp ([163.135.10.20])
by ms0.nttdata.co.jp (8.12.9/3.7W-NTTDATA-TOP-01/14/03) with ESMTP id h7K6u0h7007154
for <pgsql-hackers(at)postgresql(dot)org>; Wed, 20 Aug 2003 15:56:00 +0900 (JST)
Received: from chip.swh.nttdata.co.jp (localhost [127.0.0.1])
by mail0.nttdata.co.jp (8.12.9/3.7W-NTTDATA-TOP-11/07/02) with ESMTP id h7K6txBL015007;
Wed, 20 Aug 2003 15:55:59 +0900 (JST)
Received: from SWHEPSILON.swh.swh.nttdata.co.jp (swhzeta.swh.swh.nttdata.co.jp [10.8.190.27])
by chip.swh.nttdata.co.jp (8.11.6/8.11.6) with ESMTP id h7K6tw401308;
Wed, 20 Aug 2003 15:55:58 +0900
Received: from mariko.local ([10.8.168.145]) by SWHEPSILON.swh.swh.nttdata.co.jp with Microsoft SMTPSVC(5.0.2195.4453);
Wed, 20 Aug 2003 15:55:58 +0900
From: Koichi Suzuki <suzukikui(at)nttdata(dot)co(dot)jp>
Reply-To: suzukikui(at)nttdata(dot)co(dot)jp
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: table-level and row-level locks.
Date: Wed, 20 Aug 2003 15:58:36 +0900
User-Agent: KMail/1.5.1
References: <BAY1-F137scL9NtDEJm000038f1(at)hotmail(dot)com> <11887(dot)1057936677(at)sss(dot)pgh(dot)pa(dot)us>
In-Reply-To: <11887(dot)1057936677(at)sss(dot)pgh(dot)pa(dot)us>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200308201558(dot)36596(dot)suzukikui(at)nttdata(dot)co(dot)jp>
X-OriginalArrivalTime: 20 Aug 2003 06:55:58.0819 (UTC) FILETIME=[1C350B30:01C366E8]
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200308/924
X-Sequence-Number: 42581

Hi,

I understand this is very old topics but ...
I tried to find where such lock mark is defined in each tuple on disk, but I
failed to find such definition in include/access/htup.h. Only the bit
relevant to lock is HEAP_XMAX_UNLOGGED and I understand this bit is used only
when we have to split a big tuple into multiple blocks or to toast it.

I need to know where such "lock marks" are stored in the source level.

Any hint is appreciated.

Thanks,

Koichi Suzuki, NTT DATA Intellilink Corp.

$BEZMKF|(B 12 7$B7n(B 2003 00:17$B!"(BTom Lane $B$5$s$O=q$-$^$7$?(B:

> Please do not use HTML mail on
> this list ...
>
> Anyway, the answer to your
> question is that row locks are
> recorded on disk (by marking
> the tuple as locked). We'd
> soon run out of memory if we
> tried to record them in the
> shared lock table.
>
> regards, tom lane
>