| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Improving postgresql.conf |
| Date: | 2004-06-16 04:05:23 |
| Message-ID: | 40CFC703.5010603@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-06-16 04:53:41 | Re: OWNER TO on all objects |
| Previous Message | Tom Lane | 2004-06-16 03:27:28 | Re: Improving postgresql.conf |