Message-ID: <45AFDB27.2040502@zeut.net>
Date: Thu, 18 Jan 2007 15:40:07 -0500
From: "Matthew T. O'Connor" <matthew@zeut.net>
User-Agent: Thunderbird 2.0b1 (Windows/20061206)
MIME-Version: 1.0
To: Jeremy Haile <jhaile@fastmail.fm>
CC: pgsql-performance@postgresql.org
Subject: Re: Autoanalyze settings with zero scale factor
References: <1169145474.20103.1169962769@webmail.messagingengine.com>
	<45AFC86B.9010704@zeut.net>
	<1169151707.6247.1169971737@webmail.messagingengine.com>
In-Reply-To: <1169151707.6247.1169971737@webmail.messagingengine.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jeremy Haile wrote:
>> Also, are other auto-vacuums and auto-analyzes showing up in the 
>> pg_stats table?  Maybe it's a stats system issue.
>>     
>
> No tables have been vacuumed or analyzed today.  I had thought that this
> problem was due to my pg_autovacuum changes, but perhaps not.  I
> restarted PostgreSQL (in production - yikes)  About a minute after being
> restarted, the autovac process fired up.
>
> What could get PG in a state where autovac isn't running?  Is there
> anything I should watch to debug or monitor for this problem in the
> future?  I wish I'd noticed whether or not the stats collector process
> was running before I restarted.

First off you shouldn't need to restart PG.  When it wasn't working did 
you ever check the autovacuum_enabled setting? For example within psql: 
"show autovacuum;".

I would venture to guess that autovacuum was disabled for some reason.  
Perhaps last time you started the server the stats settings weren't enabled?