Re: Berserk Autovacuum (let's save next Mandrill)

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Berserk Autovacuum (let's save next Mandrill)
Дата
Msg-id 0495B833-B614-4170-9B67-EA88489E18EE@anarazel.de
обсуждение исходный текст
Ответ на Re: Berserk Autovacuum (let's save next Mandrill)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: Berserk Autovacuum (let's save next Mandrill)  (Chris Travers <chris.travers@adjust.com>)
Re: Berserk Autovacuum (let's save next Mandrill)  (Darafei "Komяpa" Praliaskouski <me@komzpa.net>)
Список pgsql-hackers
Hi,

On April 10, 2019 8:13:06 AM PDT, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>On 2019-Mar-31, Darafei "Komяpa" Praliaskouski wrote:
>
>> Alternative point of "if your database is super large and actively
>written,
>> you may want to set autovacuum_freeze_max_age to even smaller values
>so
>> that autovacuum load is more evenly spread over time" may be needed.
>
>I don't think it's helpful to force emergency vacuuming more
>frequently;
>quite the contrary, it's likely to cause even more issues.  We should
>tweak autovacuum to perform freezing more preemtively instead.

I still think the fundamental issue with making vacuum less painful is that the all indexes have to be read entirely.
Evenif there's not much work (say millions of rows frozen, hundreds removed). Without that issue we could vacuum much
morefrequently. And do it properly in insert only workloads. 


Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Berserk Autovacuum (let's save next Mandrill)
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Failure in contrib test _int on loach