Re: Improving postgresql.conf - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Improving postgresql.conf
Date
Msg-id 16286.1087356448@sss.pgh.pa.us
Whole thread Raw
In response to Re: Improving postgresql.conf  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Improving postgresql.conf
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> The proposal is to remove the comments from postgresql.conf (like
> Apache) so all entries will be active.  The downside is that it will not
> be possible to determine which values were modified from their defaults.

I think the latter is a nontrivial cost.  Perhaps we could address this
by extending the pg_settings view to include the compile-time-default
values for each variable, and then instead of "show us what you did to
postgresql.conf", the standard help request would beselect * from pg_settings where setting != default_setting;
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: OWNER TO on all objects
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Improving postgresql.conf