--- Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Maybe you should restate your problem so we can try to discover the
> cause.
Okay.
I will dis-able the hourly manual vacuum/analyze script that I implemented as a
work-around to
this problem to see if auto-vacuum is ever triggered.
But to start off with, here are the settings that I currently have in my
postgresql.conf for
auto-vacuum. I will post-back with any results whether I see auto-vacuum
working in 8.2.5 or not.
Thanks!
Regards,
Richard Broersma Jr.
#---------------------------------------------------------------------------
# RUNTIME STATISTICS
#---------------------------------------------------------------------------
# - Query/Index Statistics Collector -
stats_start_collector = on # needed for block or row stats
# (change requires restart)
stats_row_level = on
#---------------------------------------------------------------------------
# AUTOVACUUM PARAMETERS
#---------------------------------------------------------------------------
autovacuum = on # enable autovacuum subprocess?
# 'on' requires stats_start_collector
# and stats_row_level to also be on
autovacuum_naptime = 1min # time between autovacuum runs
autovacuum_vacuum_threshold = 100 # min # of tuple updates before
# vacuum
autovacuum_analyze_threshold = 25 # min # of tuple updates before
# analyze
autovacuum_vacuum_scale_factor = 0.002 # fraction of rel size before
# vacuum
autovacuum_analyze_scale_factor = 0.001 # fraction of rel size before
# analyze
autovacuum_freeze_max_age = 200000000 # maximum XID age before forced vacuum
# (change requires restart)
autovacuum_vacuum_cost_delay = -1 # default vacuum cost delay for
# autovacuum, -1 means use
# vacuum_cost_delay
autovacuum_vacuum_cost_limit = -1 # default vacuum cost limit for
# autovacuum, -1 means use
# vacuum_cost_limit
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
