From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Improving postgresql.conf |
Date: | 2004-06-16 15:19:56 |
Message-ID: | 22357.1087399196@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2004-06-16 15:25:07 | Re: Improving postgresql.conf |
Previous Message | Bruce Momjian | 2004-06-16 15:15:42 | Re: Improving postgresql.conf |