Re: BUG #13471: Reload with include_dir results in incorrect "contains errors" message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: andomar(at)aule(dot)net
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13471: Reload with include_dir results in incorrect "contains errors" message
Date: 2015-06-29 13:45:51
Message-ID: 26121.1435585551@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

andomar(at)aule(dot)net writes:
> 1. Create a new Postgres installation with "pg_ctl init"
> 2. In postgresql.conf, remove the comment before "include_dir = 'conf.d'"
> 3. Create a file "conf.d/extra.conf" containing "max_connections = 123"
> 4. Start Postgres with "pg_ctl start"
> 5. Reload Postgres with "pg_ctl reload"
> 6. Read the log file in pg_log; it says:
> received SIGHUP, reloading configuration files
> parameter "max_connections" cannot be changed without restarting the
> server
> configuration file "/home/wessel/test/postgresql.conf" contains errors;
> unaffected changes were applied

> But max_connections was not changed after restarting the server. These
> messages are incorrect.

Although I was correct in remembering that this had been fixed in 9.4,
it turns out it got broken again in 9.4.1 (by me :-(). I've committed
a fix that will appear in 9.4.5.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message schmidt 2015-06-30 07:57:44 BUG #13477: cant parse json into complex type
Previous Message Xavier 12 2015-06-29 12:04:43 Re: pg_xlog on a hot_stanby slave