Re: Release Notes?
| От | Pavan Deolasee |
|---|---|
| Тема | Re: Release Notes? |
| Дата | |
| Msg-id | 2e78013d0709170858p15b54d4etc71cff1c446bef0f@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Release Notes? ("Hale Boyes, Kevin " <Kevin.HaleBoyes@encana.com>) |
| Список | pgsql-advocacy |
On 9/17/07, Hale Boyes, Kevin <Kevin.HaleBoyes@encana.com> wrote:
Right. The text is based on stale information. HOT stands for Heap Only
Tuple and the restriction about not changing tuple length during
UPDATEs has been removed. HOT optimizes a special but important
case where UPDATE does not change any index key columns
or columns referenced in index expressions
and predicates. HOT helps early reclaim of dead space in a table, thus
reducing the need for frequent VACUUM and reduces relation
and index bloat.
I would suggest the following README to know more details.
http://archives.postgresql.org/pgsql-patches/2007-09/msg00261.phpChris Browne wrote:
> Let me note that a pretty nice list of features is being collected
> here: http://developer.postgresql.org/index.php/WhatsNew83
A small correction. HOT stands for Heap Only Tuple.
Right. The text is based on stale information. HOT stands for Heap Only
Tuple and the restriction about not changing tuple length during
UPDATEs has been removed. HOT optimizes a special but important
case where UPDATE does not change any index key columns
or columns referenced in index expressions
and predicates. HOT helps early reclaim of dead space in a table, thus
reducing the need for frequent VACUUM and reduces relation
and index bloat.
I would suggest the following README to know more details.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-advocacy по дате отправления: