Postgres Weekly — 2026-03, Week 12

Editor’s Note

PostgreSQL 19 continues to take shape with several operator-focused features entering the mainline, while production deployments are increasingly demonstrating that vanilla Postgres can handle workloads traditionally reserved for specialized systems. This week’s developments span command consolidation, query plan control, and architectural simplification.

Top Stories

PostgreSQL 19 Consolidates Table Maintenance with REPACK Command

The upcoming release will introduce a REPACK command that unifies the functionality previously split between VACUUM FULL and CLUSTER, separating table rewriting operations from routine maintenance vacuuming. This change aims to improve conceptual clarity for operators, though community discussion has surfaced practical migration concerns for teams running VACUUM FULL in automated production workflows. The architectural rationale centers on distinguishing lightweight cleanup from full table rewrites.

pg_plan_advice Addresses Query Plan Regressions

PostgreSQL 19 will ship with pg_plan_advice, a contrib module that allows DBAs to stabilize query plans and override planner decisions under explicit authorization. Community testing indicates this resolves a persistent operational challenge: plan regressions triggered by statistics updates, particularly in OLTP environments with complex join patterns. The framework provides controlled intervention without requiring application-level query hints or configuration tuning. Details are available in the community analysis.

OLAP Workloads Run on Standard PostgreSQL Without Dedicated Stacks

Xata has documented a product analytics data warehouse implementation built entirely on PostgreSQL using materialized views, pg_cron scheduling, and copy-on-write branching, avoiding the need for a separate OLAP system. This approach reflects two decades of PostgreSQL OLTP performance improvements that now support hybrid workloads once requiring specialized infrastructure. The implementation details demonstrate how materialized view refresh strategies and branch-based isolation can serve analytics use cases without introducing additional data movement pipelines. Separately, performance archaeology from the community confirms measurable OLTP gains over the project’s history.

Logical Replication Gets Negative Table Selection

PostgreSQL 19 adds EXCEPT TABLE syntax to CREATE PUBLICATION FOR ALL TABLES, enabling negative selection patterns for logical replication. This simplifies replication set management in dynamic environments, particularly for CloudNativePG and self-healing Kubernetes deployments where replication topology may evolve. The implementation removes the need to enumerate every included table when excluding a small subset.

Releases

pg_clickhouse 0.1.5 — Foreign data wrapper for PostgreSQL-to-ClickHouse connectivity, now available via PGXN, GitHub, and Docker. Release notes.

pg_dumpall Non-Text Formats — PostgreSQL 19 will support custom, directory, and tar output formats in pg_dumpall, generating a toc.glo file for global objects alongside per-database dumps. Feature documentation.

Worth Reading

Ultimate Guide to PostgreSQL Major Upgrades in 2026 — Comprehensive upgrade planning reference for operators managing version transitions.

pg_regresql Portable Statistics Extension — Implementation details for a statistics extension demonstrating how PostgreSQL’s planner interacts with physical page counts and selectivity ratios during query optimization.