Joshua D. Drake wrote:
> Tom Lane wrote:
>> Peter Eisentraut <peter_e@gmx.net> writes:
>>> - If we know better values, why don't we set them by default?
>>
>> The problem is: better for what?
>
> That is where some 80% solution sample config files come in.
+1.
At work I use 3 templates.
* One for salespeople's demo laptops.
* One for a developer's desktop.
* One for our bigger production servers.
The old old default postgresql.conf used to be nice for
the first group. The newer set of defaults is nicer
for the second group. Emailing the lists here's the
current best way of tuning for that last case.
I wonder if the fastest way to generate the configurator
would be to simply ask everyone to post their tuned
postgresql.conf files along with a brief description of
the use case for that file. The we could group the
use-cases into various classes; and average the values
of the submitted files. Then the configurator's one
question "choose which use case most closely matches
yours from this list".
