Deep-dives on PostgreSQL — MVCC and vacuum behaviour, reading EXPLAIN ANALYZE without guessing, index strategy for real workloads, and the subtle failure modes around long-running transactions and bloat.
4 articles · updated regularly
Each Postgres connection is a backend process with real memory cost. Past a few hundred, throughput collapses. Pooling is how you serve thousands of clients with a hundred connections.
B-Tree is the default for good reason, but reaching for it on a JSONB column or a geo query wastes the four other index types Postgres ships with. When each one wins.
The plan tells you exactly why a query is slow — if you know which numbers to trust and which to ignore.
Postgres never updates a row in place — it writes a new version and tombstones the old one. Understanding that is how you stop fearing VACUUM.