Re: postgresql.auto.conf and reload

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Christoph Berg <cb(at)df7cb(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: postgresql.auto.conf and reload
Date: 2014-06-25 13:12:51
Message-ID: CAA4eK1Log98jvFOV9wzTqpCdEWJa+5JR54TTpkiZ3XBnGJydLA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 25, 2014 at 6:11 PM, Christoph Berg <cb(at)df7cb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-06-25 13:13:29 Re: API change advice: Passing plan invalidation info from the rewriter into the planner?
Previous Message Devrim Gündüz 2014-06-25 13:10:54 pg_filedump for 9.4?