Static

PostgreSQL 19

First reported by Postgresql ·

The signal ●○○○ Compiled by AI from Postgresql and Hacker News
Why you might care

This release makes migrating existing PostgreSQL databases to version 19 more complex due to potential incompatibilities and requires specific upgrade steps. The removal of MD5 password authentication and RADIUS support will necessitate changes for users relying on these older security methods.

What happened

PostgreSQL 19 was released on November 19, 2026, introducing a suite of new features and performance enhancements. Key additions include the REPACK command for disk space reclamation and table reorganization, the pg_plan_advice and pg_stash_advice extensions for query planner control, and improved performance in areas like I/O worker scaling and foreign-key checks. Logical replication now supports enabling without a server restart and sequence value replication. Standby servers gain "read-your-writes" consistency with the new WAIT command. Autovacuum has been enhanced with parallel index processing and a new prioritization scoring system. The release also mandates a dump/restore or pg_upgrade migration, and deprecates MD5 password authentication, removing RADIUS support due to security concerns. Changes to `standard_conforming_strings`, index opclasses for inet/cidr types, and the removal of the MULE_INTERNAL encoding require careful consideration during upgrades.

What it means

PostgreSQL 19 significantly refines performance and operational efficiency, with automatic scaling of I/O workers and parallel autovacuum for indexes. The introduction of the REPACK command, especially the CONCURRENTLY option, directly addresses performance degradation from table fragmentation, offering a non-blocking solution. Enhancements to logical replication, including restartless enablement and sequence replication, streamline high-availability setups and reduce downtime for upgrades or maintenance. These changes signal a continued focus on enterprise-grade performance and manageability, catering to larger, more demanding workloads.

The release introduces critical compatibility considerations, notably the forced activation of `standard_conforming_strings` and changes to default index opclasses for `inet`/`cidr` types. These alterations mandate careful database upgrades, potentially requiring reindexing or dumps/restores for affected environments. Deprecating MD5 passwords and removing RADIUS support indicate a move towards more modern security practices, pushing users to adopt newer authentication methods. The PostgreSQL team is actively addressing performance bottlenecks and operational challenges, while also enforcing stricter standards and security postures.

AI-written summary. May contain errors.

Tech