Andrew Dunstan wrote:
> >> I still think this needs to be qualified either way. As it stands it's
> >> quite misleading. Many update scenarios will not benefit one whit from
> >> HOT updates.
> >>
> >
> > Doesn't the detail description qualify it enought? The heading isn't
> > suppose to have all the information or it would be unreadable.
> >
> >
>
> If you don't want to be more specific I'd say "certain updates" or "some
> updates" or something similar, just some flag to say it's not all of them.
Good idea. I added "most":
Heap-Only Tuples (<acronym>HOT</>) accelerate space reuse for most
<command>UPDATE</>s (Pavan Deolasee, with ideas from many others)
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
