Re: why is PG_AUTOCONF_FILENAME is pg_config_manual.h? - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: why is PG_AUTOCONF_FILENAME is pg_config_manual.h?
Date
Msg-id CAA4eK1+AOE1BqC7V=c35VWdvvTc9HZR8_T+Ao0C1OK7hM4aiag@mail.gmail.com
Whole thread Raw
In response to why is PG_AUTOCONF_FILENAME is pg_config_manual.h?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Thu, Nov 27, 2014 at 8:28 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>
> Surely that's not a value that we expect users to be able to edit.  Is
> pg_config_manual.h just abused as a place that's included everywhere?
>

Changing PG_AUTOCONF_FILENAME even by developer would
lead to loss of useful configuration settings (if any done by user via
ALTER SYSTEM) and on starting server user will see some
log message indicating that it has skipped processing configuration
file.  I think the impact of changing this define is not so severe that
someone has to do initdb, however it's non-ignorable impact.

The file header of pg_config_manual.h seems to suggest that this
file contains such parameters. 

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

pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: Re: no test programs in contrib
Next
From: Rahila Syed
Date:
Subject: Re: [REVIEW] Re: Compression of full-page-writes