Re: Table-level log_autovacuum_min_duration

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Naoya Anzai <anzai-naoya(at)mxu(dot)nes(dot)nec(dot)co(dot)jp>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Akio Iwaasa <iwaasa(at)mxs(dot)nes(dot)nec(dot)co(dot)jp>
Subject: Re: Table-level log_autovacuum_min_duration
Date: 2015-02-17 14:01:33
Message-ID: CAB7nPqTp+1CTzJchBtRxcHq2=uUYe+2aYqM0ijukSF6kKKf-4A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 17, 2015 at 5:16 PM, Naoya Anzai wrote:
> I found that definition of VERBOSE and log_autovacuum is not
> pretty match. For example, "VERBOSE" can output logs of
> scanning indices and scanning detail of analyze, but
> log_autovacuum can't output them.
> [...]

Doh. I forgot to add !IsAutoVacuumWorkerProcess() in the checks with
VACOPT_VERBOSE that I previously removed...

> And, in this v7 patch looks that VERBOSE log is always output
> in INFO-Level when log_autovacuum_min_duration is set to 0.
> Is this your point?

That's my bug, fixed in the attached.
--
Michael

Attachment Content-Type Size
20150217_autovacuum_log_relopts_v8.patch text/x-diff 15.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oskari Saarenmaa 2015-02-17 14:11:37 Re: __attribute__ for non-gcc compilers
Previous Message David Steele 2015-02-17 13:58:49 Re: pgaudit - an auditing extension for PostgreSQL