Re: HOT for PostgreSQL 8.3

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
Cc: "Hannu Krosing" <hannu(at)skype(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, <mark(at)mark(dot)mielke(dot)cc>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>, "Nikhil S" <nikhil(dot)sontakke(at)enterprisedb(dot)com>
Subject: Re: HOT for PostgreSQL 8.3
Date: 2007-02-16 16:41:32
Message-ID: E1539E0ED7043848906A8FF995BDA57901C13BF5@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Just to avoid any confusion with the patch I sent out this
> week, we are setting HEAP_UPDATE_ROOT on all tuples which are
> HOT-updated.
>
> We set HEAP_ONLY_TUPLE for all tuples which does not have
> index reference. So may be combination of (HEAP_UPDATE_ROOT &
> ~HEAP_ONLY_TUPLE) can be used to identify index referred
> tuple in a HOT-update chain.

Oh sorry. Thanks for the clarification. Imho HEAP_UPDATE_ROOT should be
renamed for this meaning then (or what does ROOT mean here ?).
Maybe HEAP_UPDATE_CHAIN ?

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2007-02-16 16:54:47 Re: patch adding new regexp functions
Previous Message Bruce Momjian 2007-02-16 16:35:32 Re: Intermittent buildfarm failures due to timestamptz test