| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | Re: Improving postgresql.conf |
| Date: | 2004-06-16 08:06:43 |
| Message-ID: | 40CFFF93.80405@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Would it help to have two lines in the config file for each setting, one
> with the default (comment) and one with the actual setting? So for
> example, the postgresql.conf would ship with something like this:
>
> #tcpip_socket = false #default
> tcpip_socket = false
Even better, have a postgresql.conf-dist file for reference.
I'm strongly in favour of distribution postresql.conf-large as well,
with much higher settings for SCSI, 1GM RAM machines, say. This is
exactly as MySQL does it and I think it's a great idea.
At least then an admin will notice the file there and say to themselves
"I wonder what I need to do to configure for a big server, i guess that
implies that this default postgresql.conf won't perform very well"...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2004-06-16 08:58:51 | Re: Improving postgresql.conf |
| Previous Message | Michael Glaesemann | 2004-06-16 07:39:16 | Re: Improving postgresql.conf |