Re: Auto vacuum

I certainly appreciate the help you've given.  Here's what the code
in this part of postgresql.conf file says.

autovacuum = on

autovacuum_naptime = 30         # time between autovacuum runs, in secs
autovacuum_vacuum_threshold = 500       # min # of tuple updates before
                                         # vacuum
autovacuum_analyze_threshold = 250      # min # of tuple updates before
                                         # analyze
autovacuum_vacuum_scale_factor = 0.2    # fraction of rel size before
                                         # vacuum
autovacuum_analyze_scale_factor = 0.1   # fraction of rel size before
                                         # analyze
autovacuum_vacuum_cost_delay = -1       # default vacuum cost delay for
                                         # autovac, -1 means use
                                         # vacuum_cost_delay
#autovacuum_vacuum_cost_limit = -1      # default vacuum cost limit for
                                         # autovac, -1 means use
                                         # vacuum_cost_limit

Thanks so much,

Carol Walter

On Apr 19, 2007, at 10:53 AM, Alvaro Herrera wrote:

> 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
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match