Re: Set visibility map bit after HOT prune

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Set visibility map bit after HOT prune
Дата
Msg-id CA+Tgmoa5XAbpOtbd1_wgaH8vC0T145VyXtspeLgxdCiWR0B60Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Set visibility map bit after HOT prune  (Simon Riggs <simon@2ndQuadrant.com>)
Ответы Re: Set visibility map bit after HOT prune
Re: Set visibility map bit after HOT prune
Список pgsql-hackers
On Wed, Dec 19, 2012 at 12:39 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> The benefit of saying that only UPDATEs clean the block is that this
> penalises only the workload making the mess, rather than everybody
> cleaning up repeatedly over one messy guy.

Right, but there are plenty of situations where having everybody clean
up after the messy guy is better than waiting around and hoping that
Mom (aka vacuum) will do it.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Set visibility map bit after HOT prune
Следующее
От: Tom Lane
Дата:
Сообщение: operator dependency of commutator and negator, redux