From: | "Matthew Nuzum" <cobalt(at)bearfruit(dot)org> |
---|---|
To: | "'Lincoln Yeoh'" <lyeoh(at)pop(dot)jaring(dot)my>, "'Matthew Nuzum'" <cobalt(at)bearfruit(dot)org> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres performance comments from a MySQL user |
Date: | 2003-06-14 00:55:12 |
Message-ID: | 002401c3320f$9d19d540$a322fea9@mattspc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Another benefit to this technique is that I get to choose the setup that I
want more easily.
For example, if I have a system capable of running "huge.conf" but postgres
isn't the main app on this server I can choose the "medium.conf" or
"small.conf" and get the results I want.
Additionally, a binary distribution will ship with all of the default
configs, while using a makefile or similar that guesses my config will be
useless when installing from RPM.
--
Matthew Nuzum
www.bearfruit.org
cobalt(at)bearfruit(dot)org
>
> Actually this sounds like a good idea to me.
>
> Type: <popular app #1>, <popular app #2>, OLAP, OLTP?
> Server: Small, Regular, Large.
>
>
> Link.
>
> At 05:33 PM 6/11/2003 -0400, Matthew Nuzum wrote:
>
> >Some databases (MySQL I think) ship several example configurations sized
> for
> >different installations. The default is very safe, but it's simply a
> matter
> >of choosing between "small.conf", "medium.conf", "big.conf", "huge.conf"
> and
> >copying it over the standard "tiny.conf" file.
> >
> >Each config file contains comments near the top of the file that specify
> >suggested hardware requirements for using it.
From | Date | Subject | |
---|---|---|---|
Next Message | weigelt | 2003-06-14 01:15:39 | Re: trigger or function? |
Previous Message | adeon | 2003-06-14 00:37:01 | trigger or function? |