Merging postgresql.conf and postgresql.auto.conf

From: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Merging postgresql.conf and postgresql.auto.conf
Date: 2015-01-14 15:31:50
Message-ID: CAD21AoDkds8Oqbr199wwrCp7fiDvOw6bbb+CGdwQHUF+gX_bVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi all,

The postgresql.auto.conf is loaded after loading of postgresql.conf
whenever configuration file is loaded or reloaded.
This means that parameter in postgresql.auto.conf is quite high
priority, so the parameter in postgresql.conf does not work at all
even if user set it manually.

If user want to change stopped postgresql server then user need to
merge two configuration file(postgresql.conf and postgresql.auto.conf)
while maintaining the consistency manually.

From an operational perspective having a written config with duplicate
entries is not good thing.
I think we need to merge two configuration file into one (or more than
one, if it uses like 'include' word)

The one solution is to add merging tool/commnand which merges two
configuration file while maintaining the consistency.
This topic have been already discussed?

Regards,

-------
Sawada Masahiko

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-01-14 15:37:56 Re: Merging postgresql.conf and postgresql.auto.conf
Previous Message Heikki Linnakangas 2015-01-14 15:30:55 Re: [PATCH] explain sortorder