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

From Tom Lane
Subject Re: Improving postgresql.conf
Date
Msg-id 22357.1087399196@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:
> Christopher Kings-Lynne wrote:
>> One thing that truly annoys me about postgresql.conf is say I unhash an 
>> option and set it to something.  Then I reload.  Then I edit the conf 
>> and hash it out again, then I reload.  Of course, the option still has 
>> my old value.  This is really annoying and I've wasted lots of time 
>> trying to figure out what's going on.

> Seems we could easily fix this by reading the config file, marking the
> entries we found, and setting all the rest to default values, basically
> pretending they were all specified as defaults in the config file.

We've discussed that and rejected it as a bad idea before.

The only real problem I see is that showing all the values as comments
encourages the idea that you can undo a change by undoing your edit.
The simple and obvious fix is to not show the values as comments ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Improving postgresql.conf
Next
From: Robert Treat
Date:
Subject: Re: Improving postgresql.conf