| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Logging pg_autovacuum |
| Date: | 2006-04-27 17:37:55 |
| Message-ID: | 200604271737.k3RHbtv00532@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> momjian(at)postgresql(dot)org (Bruce Momjian) writes:
> > Change log message about vacuuming database name from LOG to DEBUG1.
> > Prevents duplicate meaningless log messsages.
>
> Could we have some discussion about this sort of thing, rather than
> unilateral actions?
>
> Those messages were at LOG level because otherwise it's difficult to be
> sure from the log that autovac is running at all.
OK, so what do we want to do? Clearly outputing something everytime
pg_autovacuum touches a database isn't ideal. By default, the server
logs should show significant events, which this is not.
Do we want something output only the first time autovacuum runs?
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-27 17:52:40 | pgsql: Generalize mcv_selectivity() to support both VAR OP CONST and |
| Previous Message | Tom Lane | 2006-04-27 16:09:55 | Re: pgsql: Change log message about vacuuming database name from LOG to |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-04-27 17:52:54 | Re: ANSI-strict pointer aliasing rules |
| Previous Message | Taral | 2006-04-27 17:21:55 | Re: ANSI-strict pointer aliasing rules |