6 min read
Measuring and reclaiming Postgres table bloat
Table bloat is dead tuple accumulation that VACUUM has not yet reclaimed. At scale it inflates table size, slows sequential scans, and wastes I/O budget.
Read →Blog
Practical Postgres guides. No marketing copy — just queries, numbers, and fixes that work.
- 7 min read
Why autovacuum stops running and how to diagnose it
Autovacuum not running means dead tuples accumulating, table bloat growing, and eventually query plans degrading. Here is how to find out why it stopped.
Read → - 6 min read
What "idle in transaction" sessions mean and how to fix them
An "idle in transaction" session is a transaction that was opened and never closed. It holds locks, blocks autovacuum, and can stall your entire database.
Read → - 9 min read
Troubleshooting slow queries on Supabase
Supabase wraps Postgres with RLS, connection pooling, and branching — each of which adds failure modes that standard Postgres debugging guides miss. This is the actual troubleshooting path.
Read → - 7 min read
Finding missing indexes in Postgres with pg_stat_user_tables
A table doing 50,000 sequential scans per hour with 2 million rows is a maintenance ticket waiting to happen. Here's how to find those tables before they become incidents.
Read → - 8 min read
How to diagnose and fix Postgres connection pool exhaustion
When pg_stat_activity fills up and new connections start timing out, the fix is rarely 'raise max_connections'. Here's the actual diagnosis path.
Read →