From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Merging postgresql.conf and postgresql.auto.conf |
Date: | 2015-01-14 15:37:56 |
Message-ID: | 22430.1421249876@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> writes:
> 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?
Yes. The entire reason that postgresql.auto.conf is separate is that
we despaired of reading and rewriting postgresql.conf automatically
without making a hash of material in the comments. Calling the logic
a "merge tool" does not make that problem go away.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2015-01-14 15:47:19 | Re: hung backends stuck in spinlock heavy endless loop |
Previous Message | Sawada Masahiko | 2015-01-14 15:31:50 | Merging postgresql.conf and postgresql.auto.conf |