# POST 2: Reading EXPLAIN A query that ran in 20 milliseconds yesterday takes 40 seconds today. Nothing in the
Continue readingReading EXPLAIN Like a Planner: Debugging Slow Queries in PostgreSQL
# POST 1: Transactional Outbox (Slot 10 backend) You update a row in your database, then publish an event to
Continue readingThe Transactional Outbox Pattern in Go: Reliable Events Without Dual Writes
PgBouncer has quietly become mandatory infrastructure for PostgreSQL at scale. If you run more than a few hundred client connections
Every PostgreSQL developer knows the four isolation levels from the SQL standard: Read Uncommitted, Read Committed, Repeatable Read, Serializable. Fewer
Continue readingPostgreSQL Isolation Levels: What Repeatable Read Actually Guarantees
PostgreSQL takes an ACCESS EXCLUSIVE lock for most ALTER TABLE operations. That lock conflicts with everything — reads, writes, even
Every PostgreSQL backend process is a full Unix process with its own megabytes of memory. That design choice buys you
Every UPDATE in PostgreSQL is secretly an INSERT-plus-a-tombstone. The old row version stays on disk, fully readable to any transaction
Continue readingMVCC and VACUUM in PostgreSQL: Dead Tuples, Autovacuum Tuning, and What PG18 Changed
Solve the dual-write problem with one extra table and SKIP LOCKED: a working Go implementation of the transactional outbox, plus the delivery-semantics gotchas that bite in production. … Continue readingThe Transactional Outbox Pattern: Reliable Events Without Distributed Transactions
Every API that returns a list eventually has to answer the same question: how do you hand out a million
Every slow query investigation eventually reaches the same moment: you run EXPLAIN ANALYZE, and the plan makes no sense. Postgres
Continue readingReading EXPLAIN ANALYZE: Why Postgres Ignores Your Index