← Back to BLACKWIRE GHOST BUREAU VERSION UPDATE Screenshot of PostgreSQL 19 release notes highlighting new REPACK command

The PostgreSQL 19 release notes showcase the new REPACK command, a key feature for space reclamation without downtime.

POSTGRESQL 19 LAUNCHES WITH REPACK COMMAND AND SECURITY OVERHAUL

*PostgreSQL 19 drops on November 19, 2026, bringing a suite of performance boosters and hard‑line security fixes. The release reshapes replication, authentication warnings, and index defaults, forcing admins to rethink migration strategies.*

By GHOST Bureau - BLACKWIRE  |  November 20, 2026, 10:00 CET  |  PostgreSQL 19, database security, REPACK command, migration, performance

PostgreSQL 19 arrived on November 19, 2026, marking the latest major step for the open‑source database that powers countless enterprise back‑ends. The release bundles a REPACK command, new planner‑advice extensions, and a raft of security hardening measures that could reshape how organizations run and secure their data stores. Administrators face a tight window: the new defaults and deprecations force a migration plan now, or risk incompatibility with future releases. The stakes are high for any operation that depends on continuous uptime, as the new concurrent REPACK and live‑enableable logical replication promise less disruption, but only if the upgrade path is correctly navigated.

New tools and performance gains

PostgreSQL 19 adds a REPACK command that reclaims disk space and reorganizes table contents. The REPACK (CONCURRENTLY) variant runs without blocking reads or writes, directly targeting high‑availability workloads. Two extensions, pg_plan_advice and pg_stash_advice, give DBAs fine‑grained control over planner decisions and automatic application of advice. Automatic scaling of I/O worker processes, faster foreign‑key checks, and broader planning optimisations tighten query latency. Logical replication can now be toggled without a server restart when wal_level equals replica, and sequence values replicate as well. Parallel autovacuum now works on table indexes, while a new scoring system prioritises vacuum work. These changes promise measurable speedups across mixed OLTP and analytical environments.

How does PostgreSQL 19 tighten security?

The release introduces a server variable password_expiration_warning_threshold that warns users seven days before password expiry, triggered after successful MD5 authentication. MD5 passwords themselves are deprecated, and the escape_string_warning variable has been removed as unnecessary. RADIUS support, previously limited to insecure UDP, is eliminated. Database, role, and tablespace names can no longer contain carriage returns or line feeds, a move aimed at preventing obscure injection vectors. Standard_conforming_strings is forced on, breaking dumps created with older pg_dump versions that used the off setting. System columns are barred from COPY FROM ... WHERE clauses, closing a long‑standing ambiguity. Together, these measures raise the baseline security posture of any PostgreSQL deployment.

The REPACK command lets DBAs reclaim space without halting traffic – a game changer for high‑availability environments.

What migration hurdles does version 19 present?

Migrating to PostgreSQL 19 requires a dump/restore via pg_dumpall, pg_upgrade, or logical replication. Compatibility breaks include the new password_expiration_warning_threshold, the removal of the io_workers variable (replaced by four new variables), and the forced standard_conforming_strings setting, which invalidates older dumps that used the off mode. Index opclass defaults for inet and cidr shift from btree_gist to GiST, and clusters with btree_gist inet/cidr indexes are blocked from upgrade. The max_locks_per_transaction default doubles from 64 to 128, demanding configuration adjustments for legacy workloads. JIT is now disabled by default, meaning sites that rely on large analytical queries must manually enable it. Each of these changes forces administrators to audit configurations before a successful upgrade.

What operational impact will the new features have?

Logical replication can be enabled on the fly, reducing downtime for cross‑region data pipelines. The new WAIT command supplies read‑your‑writes consistency on standby servers, a critical feature for disaster‑recovery scenarios. Parallel autovacuum now shares a cost‑based delay limit across leaders and workers, preventing runaway vacuum budgets. Vacuum cost budgeting may slow parallel vacuum runs, but it protects overall system stability. The rename of sync_error_count to sync_table_error_count clarifies sequence error tracking in pg_stat_subscription_stats. Updated wait event names (BUFFER, BufferCleanup, BufferShared, etc.) give finer‑grained insight into lock contention. Collectively, these operational tweaks tighten performance predictability while demanding updated monitoring practices.

Frequently asked questions

When was PostgreSQL 19 released?

PostgreSQL 19 was released on November 19, 2026.

What new command helps reclaim disk space in PostgreSQL 19?

The new REPACK command reclaims disk space and reorganizes table contents, and REPACK (CONCURRENTLY) can run without blocking reads and writes.

How does PostgreSQL 19 improve password security?

It adds a password_expiration_warning_threshold variable that warns users seven days before password expiry after MD5 authentication, and MD5 passwords are deprecated.

PostgreSQL 19 is not a gentle polish; it is a decisive overhaul that pushes performance, security, and operational transparency forward. Teams that ignore the migration checklist risk broken dumps, failed upgrades, and exposed authentication pathways. Those that act now can leverage concurrent REPACK, live replication toggles, and refined vacuum controls to sharpen their data pipelines. The release sets a new baseline – and the database community will measure every query against it.

Sources: PostgreSQL 19 Release Notes (https://www.postgresql.org/docs/release/19.0/)