Date: Fri, 6 May 2016 13:58:30 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Thomas SIMON <tsimon@neteven.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Autovacuums not triggering anymore
Message-ID: <20160506165830.GA219913@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <a94de6dd-4521-d990-3220-2a9b10092cfd@neteven.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Thomas SIMON wrote:
> Hi all,
> 
> Since two days, autovacuum_analyze & autovacuum_vacuum does not trigger
> anymore on any of my databases (but they are started on db template1).
> Before, I had around at least 30 analyzes and 400 vacuums per hour on these
> DBs.

Are autovacuum workers all busy processing some very large?  Look for
them in pg_stat_activity.  If not, identify what is the autovacuum
launcher process doing; perhaps attach a debugger to it and see if it
ever calls launch_worker() or do_start_worker().  If time longer than
autovacuum_naptime lapses and it doesn't, have a look at the "stats
collector process"; is that one alive and working?  If you attach to it
with a debugger, you should see it operate if you do a simple query in a
session such as "select * from pg_stat_user_tables".  In that query,
also verify the autovacuum and autoanalyze timestamps.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin