Re: New IndexAM API controlling index vacuum strategies

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: New IndexAM API controlling index vacuum strategies
Дата
Msg-id CAH2-Wzn3vE04MC=XAfPnT=x4zybNLF0YRLzMYUX9GrfA_X9amg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: New IndexAM API controlling index vacuum strategies  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: New IndexAM API controlling index vacuum strategies  (Masahiko Sawada <sawada.mshk@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
On Mon, Mar 22, 2021 at 8:33 PM Peter Geoghegan <pg@bowt.ie> wrote:
> More concretely, maybe the new GUC is forced to be 1.05 of
> vacuum_freeze_table_age. Of course that scheme is a bit arbitrary --
> but so is the existing 0.95 scheme.

I meant to write 1.05 of autovacuum_vacuum_max_age. So just as
vacuum_freeze_table_age cannot really be greater than 0.95 *
autovacuum_vacuum_max_age, your new GUC cannot really be less than
1.05 * autovacuum_vacuum_max_age.

-- 
Peter Geoghegan

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: New IndexAM API controlling index vacuum strategies
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: Handling of opckeytype / CREATE OPERATOR CLASS (bug?)