Bruce Momjian <bruce@momjian.us> wrote:
> A more radical approach would be for the server to refuse to start
> if a setting is set in more than one file, and for the server to
> report both locations. That would reduce the guesswork about
> problems.
-1
I see that as a big step backward. As mentioned earlier in the
thread, we use an include at the end of postgresql.conf to point to a
file with any overrides from our standard configuration. Without the
ability to do that, managing 200 clusters would be harder.
I would not complain if the server logged duplicates. (That would
actually be a minor blessing, as the startup would log all our
deviations from standard -- at least if our standard had an explicit
entry.)
-Kevin