| From: | "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Clarification about HOT |
| Date: | 2007-11-05 15:20:33 |
| Message-ID: | 9362e74e0711050720o54477842t75a2557cc2770f93@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks Heikki. To clarify, there won't be any redirect-line pointers in this
implementation. That space is saved. We will have the index tuple point to
the latest live tuple in the update chain. So no need for redirect-line
pointers.
Thanks,
Gokul.
On 11/5/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
>
> Gokulakannan Somasundaram wrote:
> >> There's also the little problem that a redirect line pointer doesn't
> >> have room for a cross-page link,
> >
> > i don't know, what is a re-direct line pointer.
>
> Then you clearly don't understand at all how HOT works. Please go read
> src/backend/access/heap/README.HOT.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>
--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Group.
(www.alliedgroups.com)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-05 15:20:43 | plpgsql keywords are hidden reserved words |
| Previous Message | Gregory Stark | 2007-11-05 15:19:43 | Re: pgsql: Add a note about another issue that needs to be considered before |