From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | autovacuum_max_workers docs |
Date: | 2009-09-11 13:39:56 |
Message-ID: | 20090911133956.GR416@eddie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The current docs for autovacuum_max_workers suggest it should be modifiable
with a reload, unless I'm reading in awfully silly ways this morning (which
isn't entirely out of the question). Anyway, in the 8.3.7 and 8.5devel
instances I've tried, autovacuum_max_workers can only be set at server start.
I propose this:
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 7c82835..26a8ddf 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3589,8 +3589,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<para>
Specifies the maximum number of autovacuum processes (other than the
autovacuum launcher) which may be running at any one time. The default
- is three. This parameter can only be set in
- the <filename>postgresql.conf</> file or on the server command line.
+ is three. This parameter can only be set at server start.
</para>
</listitem>
</varlistentry>
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-11 14:08:32 | Re: Why does LOG have higher priority than ERROR and WARNING? |
Previous Message | Alvaro Herrera | 2009-09-11 13:23:27 | Re: RfD: more powerful "any" types |