"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> While the student could do some benchmarking on relatively new
> hardware and make suggestions, I agree with Tom. Having to keep
> support for older platforms doesn't leave much flexibility to change
> the defaults.
Another point here is that the defaults *are* reasonable for development
and for small installations; the people who are complaining are the ones
who expect to run terabyte databases without any tuning. (I exaggerate
perhaps, but the point is valid.)
We've talked more than once about offering multiple alternative
starting-point postgresql.conf files to give people an idea of what to
do for small/medium/large installations. MySQL have done that for years
and it doesn't seem that users are unable to cope with the concept.
But doing this is (a) mostly a matter of testing and documenting, not
coding and (b) probably too small for a SoC project anyway.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
