From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Release Note Changes |
Date: | 2007-12-07 17:42:58 |
Message-ID: | 200712071742.lB7Hgwf21668@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
>
> Simon Riggs wrote:
> >
> > - Heap-Only Tuples (HOT) accelerate space reuse for UPDATEs
> > change to
> > "Heap-Only Tuples (HOT) improve performance of frequent UPDATEs"
> >
> >
> >
>
> I think we need to qualify this, or it could be quite misleading.
> perhaps add "that don't affect indexed columns" or something like that.
This is covered in the detailed text below the item:
<para>
Heap-Only Tuples (<acronym>HOT</>) accelerate space reuse for
<command>UPDATE</>s (Pavan Deolasee, with ideas from many others)
</para>
<para>
<command>UPDATE</>s and <command>DELETE</>s leave dead tuples
behind, as do failed <command>INSERT</>s. Previously only
<command>VACUUM</> could reclaim space taken by dead tuples. With
<acronym>HOT</> dead tuple space can be reclaimed at the time of
<command>UPDATE</> or <command>INSERT</> if no changes are made to
indexed columns. This allows for more consistent performance.
Also, <acronym>HOT</> avoids adding duplicate index entries.
I just updated the wording so the index issue is clearer.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-12-07 18:22:10 | Re: [HACKERS] "distributed checkpoint" |
Previous Message | Bruce Momjian | 2007-12-07 17:33:29 | Re: Release Note Changes |