From: | "Selena Deckelmann" <selenamarie(at)gmail(dot)com> |
---|---|
To: | "Rich Shepard" <rshepard(at)appl-ecosys(dot)com> |
Cc: | pdxpug(at)postgresql(dot)org |
Subject: | Re: pre-algebra discussion - HOT? |
Date: | 2007-09-20 20:57:21 |
Message-ID: | 2b5e566d0709201357t54be1031tcc95360be6c526ca@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pdxpug |
[oops - sent only to Rich, and fixed attribution this time]
On 9/20/07, Rich Shepard <rshepard(at)appl-ecosys(dot)com> wrote:
> On Thu, 20 Sep 2007, Jeff Davis wrote:
>
> > I've been following HOT for a while, and I don't mind sharing. I do not
> > have in-depth knowledge on it, however.
>
> Jeff/Selena,
>
> For those of us who are NOT HOT, please explain what HOT is/does. In two
> sentences.
In one sentence:
HOT (Heap Overflow Tuple) is intended to improve update behavior on
heavily updated tables.
From Pavan Deolasee:
"HOT stands for Heap Overflow Tuple and this is an attempt to solve some
of the problems associated with frequently updated tables. This
design optimizes the updates when none of the index columns are
modified and length of the tuple remains the same after update. In this
particular case, the updated tuple is stored in a separate overflow
relation and pulled-back into the main relation when the tuple in
the main relation becomes dead."
--
Selena Deckelmann
PDXPUG - Portland PostgreSQL Users Group
http://pugs.postgresql.org/pdx
http://www.postgresqlconference.org
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2007-09-20 21:10:18 | Re: pre-algebra discussion - HOT? |
Previous Message | Rich Shepard | 2007-09-20 20:22:15 | Re: pre-algebra discussion - HOT? |