Re: postgresql.conf - Mailing list pgsql-hackers

From Rene Pijlman
Subject Re: postgresql.conf
Date
Msg-id gk6lvt05a0d8j55iqlffc0mm6a2p7jk6fh@4ax.com
Whole thread Raw
In response to Re: postgresql.conf  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Mon, 19 Nov 2001 16:04:10 -0500 (EST), you wrote:

>> What we ought to do, however, is to collect and document empirical methods
>> for tuning, such as the above "1/4 of available memory" rule (which does
>> not claim to be correct, btw.).
>
>What would be interesting is to have a program that prompted the user,
>checked some system values, and modified postgresql.conf accordingly.

I vaguely remember Oracle had an out-of-the-box choice for a
small, medium or large installation, with small being the
default. This changed a bunch of parameters, including the RDBMS
block buffers, shared global area, max open cursors and such.
This can be implemented as an (installation time) config utility
on top of the current fundamental parameters.

Regards,
René Pijlman <rene@lab.applinet.nl>


pgsql-hackers by date:

Previous
From: F Harvell
Date:
Subject: Re: bug or change in functionality in 7.2?
Next
From: mlw
Date:
Subject: Re: postgresql.conf (Proposed settings)