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

From Christopher Kings-Lynne
Subject Re: Improving postgresql.conf
Date
Msg-id 40CFC703.5010603@familyhealth.com.au
Whole thread Raw
In response to Re: Improving postgresql.conf  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Improving postgresql.conf
Re: Improving postgresql.conf
List pgsql-hackers
>>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.

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.

Chris



pgsql-hackers by date:

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