I think we've talked about this a couple times over the years, but I'm not
sure it was resolved or not.
The message post about load testing and SQLite showed PostgreSQL poorly.
Yea, I know, it was the Windows port not being optimized, I can see that,
but it raises something else. A good set of baselines for people to build
from.
Use cases: What you you intend to use PostgreSQL for.
Maybe it is a set of example postgresql.conf files that have various uses,
maybe it is a set of documtation, maybe a set of custom analyzer queries,
and more likely a combination of all of these.
One of the things that makes this interesting is that the staated goals of
the use cases and the actual settings will be exposed to a wider audience
and hence have a better chance of being further refined by people with
more experience with different aspects of postgresql.
We could provide whole postgresql.conf files for specific hardware
targets, sql scripst to alter settings, and maybe custom analyzers.
For instance:
Data loading: a configuration that will restore a pg_dump file or accept
data loading very fast.
Small footprint, limited resources.
Large server, large tables.
Large server, many small databases
Giant server, many large tables, possily many databases.
High speed static server, "balls to the wall" speed, super optimized for
query speed.
High speed dynamic server, fast as possible read/write.
Any other suggestions?
