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

Re: Autovacuum Logging

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Will Reese <wreese(at)rackspace(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Autovacuum Logging
Date: 2006-04-27 05:20:47
Message-ID: 20060427052047.GY97354@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
I believe 8.2 will have improved autovac logging. Take a look in the
-hackers archives for more info.

On Wed, Apr 26, 2006 at 10:47:26PM -0500, Will Reese wrote:
> Is there a reason many of the most useful autovacuum.c elog  
> statements are set to DEBUG2?  It seems to me that these should be  
> set to LOG.
> 
> I used autovacuum when it was a contrib module, and it failed after a  
> month.  To prevent major performance problems I went back to the  
> daily vacuum.  I was looking forward to using autovacuum in 8.1 since  
> it is more resilient and configurable now, but when I noticed it  
> would not log it's activities I almost decided against it.  After  
> looking at the source code it seems that all the necessary logging is  
> built in, it's just not set to the appropriate log level.  I'm sure  
> I'm not the only person interested in this, and I saw somewhere (I  
> can't find it again) that EnterpriseDB has enabled autovacuum  
> logging.  I don't think it's too verbose to change these to the  
> normal log level, but if so could it be a postgresql.conf option to  
> enable/disable autovacuum logging?  It sure would be nice to be able  
> to verify that tables are being vacuumed properly without having to  
> set the log level to DEBUG2.
> 
> Will Reese -- http://blog.rezra.com
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

In response to

Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2006-04-27 05:49:08
Subject: Re: [HACKERS] pg_dump
Previous:From: markDate: 2006-04-27 05:00:26
Subject: Re: ANSI-strict pointer aliasing rules

pgsql-general by date

Next:From: Jim C. NasbyDate: 2006-04-27 05:27:12
Subject: Re: Disk Failure Scenarios
Previous:From: Jim C. NasbyDate: 2006-04-27 04:52:43
Subject: Re: [HACKERS] pg_dump

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