Re: BUG #15659: missing comment "change requires restart" in postgresql.conf for parameter "data_sync_retry"

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: thomas(dot)poty(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15659: missing comment "change requires restart" in postgresql.conf for parameter "data_sync_retry"
Date: 2019-02-28 02:05:19
Message-ID: 20190228020519.GE1617@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Feb 27, 2019 at 07:24:39AM +0000, PG Bug reporting form wrote:
> In postgresql.conf, the mention of a required restart is missing for
> "data_sync_retry" parameter :
> - in the $PGDATA/postgresql.conf after an initdb
> - in /usr/pgsql-10/share/postgresql.conf.sample

You are right. I have noticed at the same time that the docs are
forgetting to mention the same and that the 80-character-limit was not
really respected, so fixed the whole and committed. There are other
places where that limit is not respected in postgresql.conf.sample,
particularly for the new recovery parameters... But well...

Thanks for the report!
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2019-02-28 07:46:57 Re: BUG #15623: Inconsistent use of default for updatable view
Previous Message Marc Dean 2019-02-28 01:01:16 Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events