I am thinking, what do we want to show by default about autovacuum in
the server logs.  What if we output a line the first time autovacuum
runs successfully on server start?

---------------------------------------------------------------------------

Bruce Momjian wrote:
> Robert Treat wrote:
> > On Thursday 27 April 2006 11:59, Bruce Momjian wrote:
> > > Well, one problem now is that everytime pg_autovacuum opens a database,
> > > a message is placed in the logs:
> > >
> > >   LOG:  autovacuum: processing database "test"
> > >   LOG:  autovacuum: processing database "test"
> > >   LOG:  autovacuum: processing database "test"
> > >   LOG:  autovacuum: processing database "test"
> > >
> > > This is certainly not desirable.  I changed the message to DEBUG1 for
> > > 8.2 with the attached patch.  
> > 
> > IMHO this is less optimal, since the default installation will provide no 
> > way 
> > for users to verify that autovacuum is running.  Currently we can direct 
> > them 
> > to look in thier log output, this way we would have to tell them to crank 
> > up 
> > logging to DEBUG1 and then look, which will of course contain a whole lot 
> > of 
> > other chatter at that level. 
> 
> Someone is working on it.
> 
> > The best solution I have seen so far is the idea of a GUC to control 
> > autovacuums chatter level.  I hope we get that becuase the above will be a 
> > regression imho. 
> 
> The purpose of the logs is not to show something _working_, but to
> report significant events.  Frankly, even with the GUC, to see it is
> working you are still going to fill up the logs with activity.
> 
> What do people want to know? ---  that autovacuum is running, or how
> often.  If it is the former, we can print something on server startup.
> 
> We don't even really log checkpoints, so logging every autovacuum seems
> strange.


-- 
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

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

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

Reply via email to