Re: postgresql.auto.conf and reload - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: postgresql.auto.conf and reload
Date
Msg-id CAA4eK1Log98jvFOV9wzTqpCdEWJa+5JR54TTpkiZ3XBnGJydLA@mail.gmail.com
Whole thread Raw
In response to postgresql.auto.conf and reload  (Christoph Berg <cb@df7cb.de>)
Responses Re: postgresql.auto.conf and reload  (Devrim Gündüz <devrim@gunduz.org>)
Re: postgresql.auto.conf and reload  (Christoph Berg <cb@df7cb.de>)
List pgsql-hackers
On Wed, Jun 25, 2014 at 6:11 PM, Christoph Berg <cb@df7cb.de> wrote:
>
> 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

This will happen without Alter System as well, if you change
the value of port in postgresql.conf and try to load conf file with SIGHUP.
You cannot reload PGC_POSTMASTER parameters without server restart.



With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Devrim Gündüz
Date:
Subject: pg_filedump for 9.4?
Next
From: Robert Haas
Date:
Subject: Re: API change advice: Passing plan invalidation info from the rewriter into the planner?