Rank PostgreSQL queries by total time, mean time, calls, I/O and temp spill with pg_stat_statements, then confirm fixes with EXPLAIN (ANALYZE, BUFFERS).
1 comment
jerrypennaabout 4 hours ago
I wrote the guide as I've had multiple performance issues after postgres on prem to AWS and oracle to postgres migrations.
I find it easier and more efficient to have the sql ready and a comprehensive performance queries.
One mistake I made was miscalculating the ratio for vacuum threshold and as a result the auto vacuum didn't run.
Any suggestions or corrections, let me know.
Read the full thread on Hacker News →
Related stories
- Hacker News · 2 points · 7 days ago
- Hacker News · 1 points · 10 days ago
- DEV Community · 10 points · 13 days ago
- Be Careful with Your Select * Queriesnotesonsystems.comHacker News · 1 points · 12 days ago
- Hacker News · 1 points · 11 days ago
- Finding Bugsmatklad.github.ioHacker News · 1 points · 11 days ago