Re: Table-level log_autovacuum_min_duration

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Re: Table-level log_autovacuum_min_duration
Дата
Msg-id CAHGQGwFq4t1j-YvJAtEPzMRYKOeGWC32Tf4utt0tVfZ61Vda=A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Table-level log_autovacuum_min_duration  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: Table-level log_autovacuum_min_duration  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
On Thu, Mar 19, 2015 at 1:43 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Thu, Mar 19, 2015 at 12:40 PM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> On Thu, Mar 19, 2015 at 12:23 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>>> Are you planning to update the patch so that it's based on the commit 0d83138?
>>
>> Yes... Very soon.
>
> And here is the rebased patch.

Thanks for rebasing the patch! Looks good to me.

One concern about this patch is; currently log_autovacuum_min_duration can be
changed even while autovacuum worker is running. So, for example, when
the admin notices that autovacuum is taking very long time, he or she can
enable logging of autovacuum activity on the fly. But this patch completely
prevents us from doing that, because, with the patch, autovacuum worker always
picks up the latest setting value at its starting time and then keeps using it
to the end. Probably I can live with this. But does anyone has other thought?

Regards,

-- 
Fujii Masao



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

Предыдущее
От: Venkata Balaji N
Дата:
Сообщение: recovery_target_time ignored ?
Следующее
От: Ashutosh Bapat
Дата:
Сообщение: Re: Display of multi-target-table Modify plan nodes in EXPLAIN