Re: Per-table log_autovacuum_min_duration is actually documented

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Per-table log_autovacuum_min_duration is actually documented
Дата
Msg-id CAB7nPqRNt0vGGU3Ud_85iijiNtvt9mSbijDwd6xavP0q1fkmqg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Per-table log_autovacuum_min_duration is actually documented  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Per-table log_autovacuum_min_duration is actually documented
Список pgsql-hackers
On Wed, Nov 11, 2015 at 12:07 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Michael Paquier <michael.paquier@gmail.com> writes:
>> This is actually documented in src/sgml/ref/create_table.sgml with the
>> following paragraph so this mention in the release notes does not seem
>> needed:
>> log_autovacuum_min_duration, toast.log_autovacuum_min_duration (integer)
>> Custom log_autovacuum_min_duration parameter.
>
> Hmm ... that doesn't seem exactly transparent; what does "custom" mean?

In this context, "custom" means a per-table value that is used instead
of the server-wide value if defined. Its toast equivalent uses the
per-table value if not defined explicitly. The other autovacuum
parameters are using the same formulation.

> Should it read "Overrides log_autovacuum_min_duration for autovacuum
> operations on this specific table or toast table"?

The same applied for all the other autovacuum and autoanalyze
parameters. Do you think that we should add in the top paragraph of
section "Storage Parameters" a mention of the type "If this parameter
has a server-wide equivalent parameter, the per-table value overrides
its server-wide equivalent if defined" or similar.
-- 
Michael



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: bootstrap pg_shseclabel in relcache initialization
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Error in char(n) example in documentation