I'm not sure if we've done a reload. I'm in an academic environment
and our department is in a state of flux right now. I'm in the
process of trying to get up to speed on postgreSQL as fast as I can.
Here is the result set from that query.
select * from pg_settings where name = 'autovacuum';
name | setting | unit | category |
short_desc |
extra_desc | context | vartype | source | min_val | max_val
------------+---------+------+------------
+-----------------------------------+-
-----------+---------+---------+--------------------+---------+---------
autovacuum | on | | Autovacuum | Starts the autovacuum
subprocess. |
| sighup | bool | configuration file | |
(1 row)
Thank you,
Carol
On Apr 19, 2007, at 4:59 PM, Robert Treat wrote:
On Thursday 19 April 2007 13:54, Carol Walter wrote:
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
Do you know if you have done a reload of the config files since
these were
changed? Try doing a select * from pg_settings where name ~
'autovacuum' to
see what your db is currently using.
--
Robert Treat
Database Architect
http://www.omniti.com
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
