Re: Frequent Update Project: Design Overview of HOT Updates

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

> If we perform an update that meets the HOT criteria then we put the
> new version into the overflow relation; we describe this as a HOT
> UPDATE. If we perform an update that does not meet the criteria, then we
> carry on with the existing/old MVCC behaviour; we describe this as a
> non-HOT UPDATE.

Making the essential performance analysis question, "Am I HOT or Not?"  

Sorry, but someone had to say it.  ;-)

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

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

Предыдущее
От: "Simon Riggs"
Дата:
Сообщение: Re: Introducing an advanced Frequent Update Optimization
Следующее
От: Christopher Browne
Дата:
Сообщение: Re: Introducing an advanced Frequent Update Optimization