I've just run into this: $ psql -p 5433 (that port is configured in postgresql.conf) # alter system set port = 5494;
... restart the server $ psql -p 5494 # select pg_reload_conf(); 2014-06-25 14:22:07 CEST [11297-4] LOG: received SIGHUP, reloading configuration files 2014-06-25 14:22:07 CEST [11297-5] LOG: parameter "port" cannot be changed without restarting the server 2014-06-25 14:22:07 CEST [11297-6] LOG: configuration file "/etc/postgresql/9.4/main/postgresql.conf" contains errors; unaffected changes were applied I think reloading shouldn't be nagging me about parameters in postgresql.conf that are going to be overwritten in postgresql.auto.conf. Reloading again will issue the warnings again... It's true that my config has two contradicting settings in there now, but if that's not an issue at server start, it shouldn't be one for reloading either. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
