Re: Frequent Update Project: Design Overview of HOTUpdates

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: Frequent Update Project: Design Overview of HOTUpdates
Дата
Msg-id 2e78013d0611100612h3285ca31x68ef3ab2be136638@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Frequent Update Project: Design Overview of HOTUpdates  ("Simon Riggs" <simon@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения


On 11/10/06, Simon Riggs <simon@2ndquadrant.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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Simon Riggs"
Дата:
Сообщение: Re: Frequent Update Project: Design Overview of HOTUpdates
Следующее
От: "Zeugswetter Andreas ADI SD"
Дата:
Сообщение: Re: Frequent Update Project: Design Overview of HOT Updates