Re: More logging for autovacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, Gregory Stark <stark(at)enterprisedb(dot)com>
Subject: Re: More logging for autovacuum
Date: 2007-08-07 17:12:18
Message-ID: 23590.1186506738@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> With 8.3 having autovacuum on by default, we really should be logging at
> a mininum:

> autovacuum start
> autovacuum working (what am I working on but not what I am doing,
> meaning we don't need tuple information etc..)
> autovacuum stop

> Yes, by default or at least at no level higher than INFO.

No, NOT by default. Our users have made it perfectly clear that they
don't want the logs cluttered with high-volume information about
non-error normal workings of the system. Every time we have caused
the system to emit such data by default, the log level of the messages
in question has gotten dialed down in a later release.

I don't object to what Greg suggests as an option. If we try to make
it the default behavior, we will find ourselves changing that.

As far as the debug/info/etc discussion goes: if there is a GUC variable
controlling it, just make the elevel be LOG.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2007-08-07 17:38:54 Re: More logging for autovacuum
Previous Message Mark Mielke 2007-08-07 16:55:25 Re: HOT pgbench results