From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] HOT WIP Patch - version 2 |
Date: | 2007-02-20 14:43:44 |
Message-ID: | 200702201443.l1KEhjE20912@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Pavan Deolasee wrote:
> On 2/20/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > Pavan Deolasee wrote:
> > > When following a HOT-update chain from the index fetch, if we notice
> > that
> > > the root tuple is dead and it is HOT-updated, we try to prune the chain
> > to
> > > the smallest possible length. To do that, the share lock is upgraded to
> > an
> > > exclusive lock and the tuple chain is followed till we find a
> > > live/recently-dead
> > > tuple. At that point, the root t_ctid is made point to that tuple. In
> > order
> >
> > I assume you meant recently-dead here, rather than live/recently-dead,
> > because we aren't going to change live ctids, right?
>
>
> No, I meant live or recently-dead (in fact, anything other than
> HEAPTUPLE_DEAD
> or HEAPTUPLE_DEAD_CHAIN).
>
> We are not changing the tids here, but only pruning the HOT-update chain.
> After pruning, the root->t_ctid points to the oldest tuple that might be
> visible to any backend. The live tuples are still identified by their
> original tid and index reachable from the root tuple.
I am confused. Where is the root->t_ctid stored?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-02-20 14:50:40 | Re: [HACKERS] HOT WIP Patch - version 2 |
Previous Message | Pavan Deolasee | 2007-02-20 14:38:24 | Re: [HACKERS] HOT WIP Patch - version 2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-02-20 14:50:40 | Re: [HACKERS] HOT WIP Patch - version 2 |
Previous Message | Pavan Deolasee | 2007-02-20 14:38:24 | Re: [HACKERS] HOT WIP Patch - version 2 |