Re: Alter system and reload causes bogus complaints about setting changes

>"/etc/postgresql/9.4/main/postgresql.conf" contains errors; unaffected
the reason is that :
some config parameter changed need restart the pg server.
so when you reload ,there may be this error info

At 2014-07-03 05:16:56, "Mark Kirkwood" <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> wrote:
>Hi all, playing with 9.4 beta:
>
>Consider:
>
>$ cat config.sql
>ALTER SYSTEM SET max_connections = 200;
>ALTER SYSTEM SET shared_buffers = "10GB";
>ALTER SYSTEM SET maintenance_work_mem = "1GB";
>ALTER SYSTEM SET effective_io_concurrency = 10;
>ALTER SYSTEM SET wal_buffers = "32MB";
>ALTER SYSTEM SET checkpoint_segments = 192;
>ALTER SYSTEM SET checkpoint_completion_target = 0.8;
>
>$ psql < config.sql
>
>$ service postgresql restart
>
>$ psql
>ALTER SYSTEM SET checkpoint_segments = 384;
>\q
>
>$ service postgresql reload
>
>$ tail /var/log/postgresql/postgresql-9.4-main.log
>2014-07-03 08:09:40 AST LOG: received SIGHUP, reloading configuration files
>2014-07-03 08:09:40 AST LOG: parameter "max_connections" cannot be
>changed without restarting the server
>2014-07-03 08:09:40 AST LOG: parameter "shared_buffers" cannot be
>changed without restarting the server
>2014-07-03 08:09:40 AST LOG: parameter "checkpoint_segments" changed to
>"1920"
>2014-07-03 08:09:40 AST LOG: configuration file
>"/etc/postgresql/9.4/main/postgresql.conf" contains errors; unaffected
>changes were applied
>
>
>Hmmm - I didn't actually change the settings it is complaining
>about...and it is referring to the wrong file too. While this is hardly
>serious, it is likely to be immensely confusing for folk who have not
>been actively following the new changes for 9.4 (ahem...that could be a
>lot of people). It would be good to fix this before we end beta.
>
>Cheers
>
>Mark
>
>
>--
>Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-bugs