Peter Eisentraut <peter_e@gmx.net> writes:
> There is a compromise that I think we cannot make. For production
> deployment, shared buffers are typically sized at about 10% to 25% of
> available phyiscal memory. I don't think we want to have a default
> installation of PostgreSQL that takes 10% or more of memory just like
> that. It just doesn't look good.
The fundamental issue there is "box dedicated to (one instance of)
Postgres" versus "box serves multiple uses". If you don't know what
fraction of the machine resources you're supposed to take up, it's
difficult to be very smart. I think that we have to default to a
socially friendly "don't eat the whole box" position ...
regards, tom lane
