Re: Table-level log_autovacuum_min_duration - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Table-level log_autovacuum_min_duration
Date
Msg-id CAHGQGwF386sBAjn388vBkFD4-Of3BGVj4ingmiY-7A5MR9rzkQ@mail.gmail.com
Whole thread Raw
In response to Re: Table-level log_autovacuum_min_duration  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Table-level log_autovacuum_min_duration  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Thu, Mar 5, 2015 at 9:49 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Thu, Mar 5, 2015 at 7:10 PM, Fujii Masao wrote:
>> With the patch, VACUUM ANALYZE VERBOSE doesn't emit any verbose message.
>> Why did you remove that functionality?
>
> Oops. Sorry about that. In gram.y, the combination of VacuumStmt with
> AnalyzeStmt overwrote the value of log_min_duration incorrectly. I
> also found another bug related to logging of ANALYZE not working
> correctly because of the use of IsAutoVacuumWorkerProcess() instead of
> VACOPT_VERBOSE (this is reducing the diffs of the patch btw). All
> those things are fixed in the attached.

Thanks for updating the patch!

Why does log_min_duration need to be set even when manual VACUUM command is
executed? Per the latest version of the patch, log_min_duration is checked only
when the process is autovacuum worker. So ISTM that log_min_duration doesn't
need to be set in gram.y. It's even confusing to me. Or if you're going to
implement something like "VACUUM VERBOSE DURATION n" (i.e., verbose message
is output if n seconds have been elapsed), that might be necessary, though...

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Strange assertion using VACOPT_FREEZE in vacuum.c
Next
From: Michael Paquier
Date:
Subject: Re: Table-level log_autovacuum_min_duration