Re: max_worker_processes missing some documentation

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: max_worker_processes missing some documentation
Date: 2016-05-03 14:44:09
Message-ID: CA+TgmoYtsspvHyTK8OWAxDn3HFjUakaW+5r7erxR=Lzx6nhy7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 2, 2016 at 2:46 PM, Julien Rouhaud
<julien(dot)rouhaud(at)dalibo(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-05-03 14:51:04 Re: Need help debugging why autovacuum seems "stuck" -- until I use superuser to vacuum freeze pg_database
Previous Message dandl 2016-05-03 14:39:05 Re: SPI_exec ERROR in pl/r of R 3.2.4 on PostgreSQL on Windows 7