From: | Andomar <andomar(at)aule(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Include.d and warnings |
Date: | 2015-06-25 08:04:31 |
Message-ID: | 558BB60F.7020905@aule.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>> 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" causes the error message to appear.
Is anyone else willing to try and reproduce the problem?
> Just for my edification. If an include file contains a different
> value for a setting that can only be changed on restart, Postgres is
> supposed to throw out the restart message?
To clarify, the server is started with the setting already present:
postgresql.conf : max_connections 100
conf.d/extra.conf : max_connections 125
If you start the server and reload, this will give the error message.
Checking the live setting with "select * from pg_settings where name =
'max_connections'" shows that the setting already is 125. So the
warning is confusing because a restart would not change anything.
Kind regards,
Andomar
From | Date | Subject | |
---|---|---|---|
Next Message | Piotr Gasidło | 2015-06-25 12:54:47 | When files in pg_multixact/{members,offsets} get recycled? |
Previous Message | litu16 | 2015-06-25 04:11:24 | Get the difference between two timestamp cells but in a special format in PostgreSQL |