Stormatics

Key takeawaysSpeed is the wrong finish line. If moving the date by a week buys you a clean cutover, move it.Define success in numbers first: zero rows lost, a recovery time objective, a signed-off cutover window. Let the downtime budget pick your method,

Key takeawaysA routine OS patch can take Postgres offline even when Postgres itself was never touched. Here's what rolling OS patching on a proper HA cluster changes:OS-level patches (kernel, glibc, container runtime, storage driver) can take Postgres dow

On August 13, 2026, PostgreSQL shipped its biggest security release ever: 28 CVEs closed in a single day. The old record was 11.The community has done its job, a phenomenal one at that! If you run PostgreSQL for critical workloads in production, the numbe

A small setting most teams either ignore or guess at. Here's the quick version, then the full breakdown.Key TakeawaysFillfactor sets how full Postgres packs each table page on write, leaving the rest as free space for future updates to land in-place (HOT

How CloudNativePG's operator model handles failover, security, and backups on Kubernetes, and how it compares to Patroni and pgpool-II.Key TakeawaysCloudNativePG splits into two roles: an operator that manages the cluster's lifecycle, and Postgres itself

How a systematic, evidence-first approach to database performance tuning uncovered, and helped fix, a compounding set of issues on a fast-growing social analytics platform's PostgreSQL instance. Key TakeawaysDiagnosed a production PostgreSQL instance gene

Partitioning gets sold as a performance switch. You flip it on a big table, and the slow queries get fast. Most of the time, that is exactly what happens. But there is a version of this where you do all the work, split a huge table into clean partitions,

"The database is locked up." We heard some version of that sentence more than once this past week, from the same team, about what looked like the same problem. It was not the same problem. Once, Postgres had genuinely stopped responding. Every other time,

Giving an external team access to your PostgreSQL database is one of those decisions that deserves a little thought. The easiest option is to hand over a superuser account, but it's rarely the right one. A better approach is to create a dedicated role wit

When you are upgrading across major PostgreSQL versions, there are a few ways to go. Dump and restore is the simplest to reason about, but downtime scales directly with database size, so for anything multi-terabyte, it is off the table. Logical replicatio