We work for some of the largest PostgreSQL database infrastructure globally, Often we get query on how to configure PostgreSQL for performance, scalability and reliability so thought will write a post on configuring PostgreSQL for performance. PostgreSQL is a highly tunable database system but setting wrong values for PostgreSQL configuration parameters will negatively impact your overall PostgreSQL performance. Setting too high values won’t be always good for PostgreSQL performance so we strongly recommend to understand the sizing of configuration parameters before changing their default values. Please don’t consider this post a generic PostgreSQL configuration run-book or recommendations for your production infrastructure, You can definitely use this as a checklist for configuring your PostgreSQL infrastructure, This post covers tuning PostgreSQL configuration parameters like max_connections<\/a><\/span>, shared_buffers<\/a><\/span>, effective_cache_size<\/a><\/span>, work_mem<\/a><\/span>, maintenance_work_mem<\/a><\/span>, seq_page_cost<\/a><\/span>, random_page_cost<\/a><\/span>, wal_buffers<\/a><\/span>, autovacuum etc<\/a><\/span>. Below we have explained how this post \/ presentation is organized:<\/p>\n Download our featured whitepaper on configuring PostgreSQL for performance. If you\u2019re a PostgreSQL DBA or an technology executive looking to improve performance and prepare for high traffic PostgreSQL infrastructure, this is a must-read!<\/p>\n\n