max_worker_processes missing some documentation
Started by Julien Rouhaudover 9 years ago2 messages
I noticed that postgresql.conf.sample doesn't say that changing
max_worker_processes requires a restart.
Patch attached.
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
Attachments:
max_worker_process_sample.difftext/x-diff; name=max_worker_process_sample.diffDownload
diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
index e6c6591..2d2db7e 100644
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -166,7 +166,7 @@
# - Asynchronous Behavior -
#effective_io_concurrency = 1 # 1-1000; 0 disables prefetching
-#max_worker_processes = 8
+#max_worker_processes = 8 # (change requires restart)
#max_parallel_degree = 2 # max number of worker processes per node
#old_snapshot_threshold = -1 # 1min-60d; -1 disables; 0 is immediate
# (change requires restart)
Re: max_worker_processes missing some documentation
On Mon, May 2, 2016 at 2:46 PM, Julien Rouhaud
<julien.rouhaud@dalibo.com> wrote:
I noticed that postgresql.conf.sample doesn't say that changing
max_worker_processes requires a restart.Patch attached.
Good catch. Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers