| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Frequent Update Project: Design Overview of HOTUpdates |
| Date: | 2006-11-10 14:12:26 |
| Message-ID: | 2e78013d0611100612h3285ca31x68ef3ab2be136638@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/10/06, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> On Fri, 2006-11-10 at 12:32 +0100, Zeugswetter Andreas ADI SD wrote:
> e.g. a different header seems no easier in overflow than in heap
>
> True. The idea there is that we can turn frequent update on/off fairly
> easily for normal tables since there are no tuple format changes in the
> main heap. It also allows HOT to avoid wasting space when a table is
> heavily updated in certain places only.
>
>
I general though, it would make implementation a bit simpler when tuples
with
different header are isolated in a different relation.
Regards,
Pavan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas ADI SD | 2006-11-10 14:34:25 | Re: Frequent Update Project: Design Overview of HOT Updates |
| Previous Message | Simon Riggs | 2006-11-10 13:53:09 | Re: Frequent Update Project: Design Overview of HOTUpdates |