Skip site navigation (1) Skip section navigation (2)

Logging pg_autovacuum

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-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

  + If your life is a hard drive, Christ can be your backup. +

In response to


pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2006-04-27 17:52:54
Subject: Re: ANSI-strict pointer aliasing rules
Previous:From: TaralDate: 2006-04-27 17:21:55
Subject: Re: ANSI-strict pointer aliasing rules

pgsql-committers by date

Next:From: Tom LaneDate: 2006-04-27 17:52:40
Subject: pgsql: Generalize mcv_selectivity() to support both VAR OP CONST and
Previous:From: Tom LaneDate: 2006-04-27 16:09:55
Subject: Re: pgsql: Change log message about vacuuming database name from LOG to

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group