PostgreSQL Connection Pooling in Go: Sizing pgxpool, Reading Its Stats, and When PgBouncer Earns Its Keep
Every Go service that talks to PostgreSQL ends up managing a pool of database connections, and almost every team gets
Every Go service that talks to PostgreSQL ends up managing a pool of database connections, and almost every team gets
Ask a PostgreSQL database administrator what kills databases in production and you’ll hear about wraparound — the event where a
Replica lag is one of those distributed-systems facts everyone accepts in the abstract and nobody plans for in the code.
Every team seems to arrive at the same configuration at some point: the database feels slow, someone searches for a
Continue readingConnection Pool Sizing: The Math That Says Fewer, Not More
Offset pagination is the first thing everyone learns and the first thing that falls over in production. The product manager
Continue readingBeyond OFFSET: Keyset Pagination in PostgreSQL That Actually Scales
Every schema migration is easy the first time, when the table is empty and the only user is your test
Continue readingZero-Downtime PostgreSQL Migrations: Locks, Rewrites, and Expand-and-Contract
PgBouncer has quietly become mandatory infrastructure for PostgreSQL at scale. If you run more than a few hundred client connections
Every analytics dashboard has one question that looks trivial and isn’t: how many unique users did this? You can run
Continue readingHyperLogLog: Counting a Billion Uniques in 1.5 KB of Memory
Sooner or later, every API designer hits the pagination wall. The endpoint works fine in staging, then production traffic arrives
Continue readingAPI Pagination Strategies: Offset, Cursor, and Relay Connections Done Right
PostgreSQL takes an ACCESS EXCLUSIVE lock for most ALTER TABLE operations. That lock conflicts with everything — reads, writes, even