PostgreSQL Configuration for Humans
summary
PostgreSQL ships with ~270 tunable parameters and a 650‑line sample postgresql.conf, and changing about 15 settings on an 8GB/2CPU EC2 instance raises throughput by 40–50% TPS while keeping latency lower; indiscriminately increasing max_connections spikes latency to ~1.5s, so use a pooler and aim for ~50–100 usable connections. Guidance covers shared_buffers, work_mem, autovacuum/maintenance_work_mem, checkpoint/ bgwriter tuning, random_page_cost for SSDs, and a new drag-and-drop web UI that generates recommendations and a REST API (beta).
AI-written summary · about
chapters (26)
- 0:00Introduction
- 6:00Reasons to tune
- 7:50Performance tuning
- 9:05Performance comparison
- 10:15Latency
- 10:45Tuning
- 12:30tunable parameters
- 12:45some ideas
- 13:55executable
- 19:15connectionpooler
- 21:48shared buffers
- 23:35workmaam
- 28:13max parameters
- 30:00autovacuum
- 32:46tuning autovacuum
- 33:48tuning backgroundwriter
- 35:43logging
- 36:33password encryption
- 39:16PGTune
- 40:13PostgreSQL Code F
- 41:49Beta Testers
- 42:14Large Table
- 43:11Troubleshooting Slow Queries
- 47:14Vacuum Tuning
- 48:55Synchronous Commit
- 50:49SSD Parameters
related talks
34mTuning PostgreSQL to work even better
45mProper PostgreSQL Parameters to Prevent Poor Performance
33mTuning PostgreSQL to work even better
53mPostgreSQL Configuration for Humans
57mPostgreSQL When It's Not Your Job
43mPostgres Performance: From Slow to Pro
25mScaling PostgreSQL Beyond Query Optimization
26mLinux and PostgreSQL in the Multiverse of Connections