| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
| 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:11:26 |
| Message-ID: | 2e78013d0702160811y436df049t1ade9e465dcd2778@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/16/07, Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at> wrote:
>
>
> > > As described, you've made
> > > that problem worse because you're trying to say we don't know which
> of
> > > the chain entries is pointed at.
> >
> > There should be a flag, say HOT_CHAIN_ENTRY for the tuple the
>
> it's called HEAP_UPDATE_ROOT
>
>
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.
Thanks,
Pavan
--
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-16 16:35:32 | Re: Intermittent buildfarm failures due to timestamptz test |
| Previous Message | David Fetter | 2007-02-16 16:11:21 | Re: patch adding new regexp functions |