Tag
PostgreSQL 19 fixes three long-standing operational headaches. Each fix also introduces exactly one trap that only shows up at production scale.
B-tree is the default, but it is the wrong choice more often than you expect. This guide covers all six Postgres index types, the bug each was built to prevent, and the gotcha that disables each one silently.
In 2026 Postgres is the right default for almost every new project. But three specific workloads still favour MySQL — and migrating an existing codebase is rarely worth it without a concrete pain point.
Most Postgres schema changes that cause outages aren't dangerous by nature — they're dangerous because the table is large. Here's what lock each DDL operation takes and the exact patterns to make them safe.
Most Postgres users never touch isolation levels — until a double-charge or an oversold booking forces the question. What each level allows, and the production bug that follows when you pick the wrong one.
Most Postgres performance problems have a better fix than yet another B-tree index. A guide to choosing between B-tree, BRIN, GIN, and partial indexes — by matching index type to query pattern, not by guessing.
The Redis licence change created a three-way choice. Most teams are making it based on benchmarks. The real decision factors are licencing risk, ecosystem backing, and cloud-provider alignment.
Practical guides, product updates, and compliance notes — straight to your inbox. No fluff.
Newsletter is opening soon. We'll switch this on once we've got our first issue ready.