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@bearfruit.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.
