But max_connections did not change before the reload. It is just
overruled in an included configuration file.
This is fixed in 9.4 and up. Since it's just cosmetic, we did not
back-patch the change.
We're running 9.4.4. I've just tested this, and doing a "restart"
followed by a "reload" cau
On 06/24/2015 07:43 AM, Tom Lane wrote:
Andomar writes:
We've set up an include directory in postgresql.conf:
include_dir = 'conf.d'
The include directory has a file that changes the value of
"max_connections".
Now when we reload Postgres, an error appears in the logs:
-
para
Andomar writes:
> We've set up an include directory in postgresql.conf:
> include_dir = 'conf.d'
> The include directory has a file that changes the value of
> "max_connections".
> Now when we reload Postgres, an error appears in the logs:
> -
> parameter ""max_connections"" cannot be
On 06/24/2015 02:01 AM, Andomar wrote:
We've set up an include directory in postgresql.conf:
include_dir = 'conf.d'
The include directory has a file that changes the value of
"max_connections".
Now when we reload Postgres, an error appears in the logs:
-
parameter ""max_connections""
