Modified wording patch applied. Thanks.
---------------------------------------------------------------------------
David Wheeler wrote:
> PostgreSQLers,
>
> I just ran into an issue where a client thought that autovacuum was
> running but it wasn't. This is because it's not fatal when autovacuum
> is on but stats_start_collector and/or stats_row_level is off. I
> suspect that there's a reason that it's not fatal, so I thought that
> it might be useful to give folks just a little bit of help by telling
> them in postgresql.conf that they need to enable them in order for
> autovacuum to work.
>
> If this patch is not correctly formatted or against the proper file,
> please let me know and I'll make the necessary modifications.
>
> Thanks,
>
> David
>
[ Attachment, skipping... ]
>
> ---------------------------(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
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: src/backend/utils/misc/postgresql.conf.sample
===================================================================
RCS file: /cvsroot/pgsql/src/backend/utils/misc/postgresql.conf.sample,v
retrieving revision 1.194
diff -c -c -r1.194 postgresql.conf.sample
*** src/backend/utils/misc/postgresql.conf.sample 25 Sep 2006 22:12:24 -0000 1.194
--- src/backend/utils/misc/postgresql.conf.sample 3 Oct 2006 00:37:48 -0000
***************
*** 362,367 ****
--- 362,369 ----
#---------------------------------------------------------------------------
#autovacuum = off # 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 = 500 # min # of tuple updates before
# vacuum
