Re: Improving postgresql.conf

Stephen Frost wrote:

>* Greg Stark (gsstark@mit.edu) wrote:
>  
>
>>Tom Lane <tgl@sss.pgh.pa.us> writes:
>>    
>>
>>>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 ...
>>>      
>>>
>>Well even if you don't show them (and it would be most frustrating for users
>>if you don't) it's certainly expected that commenting something out returns it
>>to the default value. It's how just about every other piece of software works.
>>I can lend my own experience as one data point that I was totally surprised
>>when I found out it didn't work the way I expected.
>>    
>>
>
>I was suprised too.  I havn't tested yet, but do even other things act
>this way?  I'm thinking mainly of pg_hba.conf which I didn't think did,
>but not sure.
>
>  
>


pg_hba.conf doesn't have any default values ... if you change it all 
your old settings are blown away and the new settings get loaded. 
Commenting out a line does not leave the previous effect of that line in 
place (and it would be a major security problem if it did)

cheers

andrew