Re: : Tracking Full Table Scans

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: : Tracking Full Table Scans
Дата
Msg-id 4E81BE6F02000025000417EF@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: : Tracking Full Table Scans  (Venkat Balaji <venkat.balaji@verse.in>)
Ответы Re: : Tracking Full Table Scans  (Venkat Balaji <venkat.balaji@verse.in>)
Список pgsql-performance
Venkat Balaji <venkat.balaji@verse.in> wrote:

> I would like to know the difference between "n_tup_upd" and
> "n_tup_hot_upd".

A HOT update is used when none of the updated columns are used in an
index and there is room for the new tuple (version of the row) on
the same page as the old tuple.  This is faster for a number of
reasons, and cleanup of the old tuple is a little different.

If you want the gory implementation details, take a look at this
file in the source tree:

src/backend/access/heap/README.HOT

-Kevin

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

Предыдущее
От: Timothy Garnett
Дата:
Сообщение: Re: Performance Anomaly with "col in (A,B)" vs. "col = A OR col = B" ver. 9.0.3
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: postgres constraint triggers