From: | Mark Kirkwood <markir(at)coretech(dot)co(dot)nz> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Michael Glaesemann <grzm(at)myrealbox(dot)com>, 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:58:51 |
Message-ID: | 40D00BCB.2090009@coretech.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
This seems like a nice idea -
It might even be worth targeting a couple pf specific "ranges" - e.g :
machines with 1G RAM and 4G RAM ( "medium" are "large" come to mind, I
know it's a bit like that "other" database product we know of.... but
that doesn't mean it's necessarily bad!)
Mark
Christopher Kings-Lynne wrote:
>
>
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2004-06-16 09:10:11 | Re: Improving postgresql.conf |
Previous Message | Christopher Kings-Lynne | 2004-06-16 08:06:43 | Re: Improving postgresql.conf |