PostgreSQL 18 can be built with libnuma support. Part 3 of our NUMA series explains what Tomas Vondra's patch set changes and which tuning advice still applies.
A narrow backfill into compressed TimescaleDB chunks can still decompress far more data than expected. This workflow keeps every batch bounded, vacuumed, and recompressed.
Part 1 of a live Patroni-to-EFM migration: how a trigger-based capture table closes a silent data-loss race, and how low-cost PostgreSQL logical replication monitoring tracks drift between source and target.
When every PostgreSQL setting is right and reads are still slow, look at the storage underneath. Four Azure disk traps, from the 4 TiB caching cliff to VM I/O caps, and how to spot them.
Four production tables, two very different partitioning strategies. See how real dependency and skew data, not convention, shaped a zero-downtime migration, and the two silent bugs caught before they ever reached production.
Speed is the wrong finish line for a mission-critical PostgreSQL migration. This field-tested method covers defining success in numbers, validating data at three checkpoints, rehearsing against a production copy, following a runbook, and keeping a rollback path open until sign-off.
Why a routine kernel or glibc update keeps taking databases down, and how a rolling, node-by-node OS patch on a Patroni-managed cluster keeps Postgres up through every reboot.
PostgreSQL's August 2026 release closed 28 CVEs in a single day, a record. The fix itself is a fast binary swap. What actually determines your risk is how long it takes you to apply it. Here's how to set a patch SLA and hit it without breaking production.
Fillfactor is one of those settings people either leave alone or guess at. Here's how to calculate a real starting number from your own table data, with the formula and a query to run it.