From: Alvaro Herrera <alvherre@commandprompt.com>
To: Carol Walter <walterc@indiana.edu>
Cc: Robert Treat <robert@omniti.com>
Cc: pgsql-admin@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Auto vacuum
Date: Thu, 19 Apr 2007 10:53:20 -0400
Message-ID: <20070419145320.GD8402@alvh.no-ip.org> (raw)
In-Reply-To: <12A54BAC-0218-40F8-9A8A-26C6268D1617@indiana.edu>
References: <DFF8F759-C7C6-4092-BCB9-C7571E1C07E9@indiana.edu>
<E28DBA41-80C6-40FB-9D4B-141FF3E53A8A@indiana.edu>
<12357.1176841845@sss.pgh.pa.us>
<200704172157.54249.robert@omniti.com>
<12A54BAC-0218-40F8-9A8A-26C6268D1617@indiana.edu>
Carol Walter wrote:
> Robert,
>
> I did as you suggested and the values for autovacuum are null,
> therefore I'm guessing it isn't running. Since postgres reports that
> it is running, what other things might keep in from running?
Too high thresholds? All tables disabled in pg_autovacuum? naptime set
too high?
I suggest you turn log_min_messages more verbose, to DEBUG2, and see if
there are any entries in there regarding autovacuum. If it's running,
you would see it. You would get a message after autovacuum_naptime
seconds.
How long is autovacuum_naptime anyway?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, walterc@indiana.edu, robert@omniti.com, tgl@sss.pgh.pa.us
Subject: Re: Auto vacuum
In-Reply-To: <20070419145320.GD8402@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox