On Thu, Aug 12, 2010 at 8:42 PM, Joshua D. Drake <jd@xxxxxxxxxxxxxxxxx> wrote: > > GOOD PERFORMANCE IS ALWAYS RELIANT ON PROPER HARDWARE, DATABASE DESIGN > AND APPLICATION ARCHITECTURE. THIS TABLE IS A HINT ONLY. YOU WILL LIKELY > HAVE TO TUNE BEYOND THIS. > > shared_buffers = 25% of available memory > work_mem = 2-4MB (test using explain analyze) > effective_cache_size = 50-60% of available memory INCLUDING > shared_buffers There was also a point about making the installer create a recommended postgresql.conf file. After installation when the server is started for the first time, try to start with postgresql.conf.suggested If it starts successfully, let the user know that the server is started with a configuration file tuned for the specific system resources. Also warn about the pitfalls. If it fails to start, then fall back to default postgresql.conf and tell the user to configure manually (using pgtune) for optimum performance. Is this doable? Ma Sivakumar http://masivakumar.blogspot.com -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
