heuristics that initdb could apply. We'd have to let all of these
degrade nicely, so that even if the user select the machine hog setting,
if we find we can only do something like the tiny setting that's what
s/he would get. Also, we might need to have some tolerably portable way
of finding out about machine resources. And power users will still want
to tube things more. But it might help to alleviate our undeserved
reputation for poor performance if we provide some help to start off at
least in the right ballpark.
I think we should just do what MySQL does and include:
postgresql.conf
postgresql-large.conf
postgresql-huge.conf
Chris
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
