PostgreSQL 19 is Here: Worth the Wait
PostgreSQL 19 was released today. pgEdge packages for it are available the same day across all of our supported deployments - including Spock, where PG 19 support is already available. I have been testing the release candidates for a few weeks, so here is what I think matters most to DBAs and teams.
REPACK replaces VACUUM FULL and CLUSTER, and with the CONCURRENTLY option it rebuilds a bloated table without blocking reads and writes. In my own test, inserts kept running at about 2,000 a second with no failed transactions while a bloated table was rebuilt in under a second. It needs a primary key or replica identity index, and it is not MVCC safe for transactions that started before the swap. Shaun Thomas wrote a blog on the topic - give it a read for more detail.
Logical replication gets the biggest changes for anyone running replicated clusters. Sequences can now be published with ALL SEQUENCES and synced with REFRESH SEQUENCES, which removes the manual setval step from migrations and upgrades. Logical replication can also be turned on without a restart when wal_level is replica. Subscriptions get retain_dead_tuples for better conflict detection, and publications can leave tables out with EXCEPT.
On the operations side, autovacuum can now use parallel workers on indexes and ranks tables with a scoring system, so the ones that need it most go first. The pg_plan_advice and pg_stash_advice extensions let you steer the planner and keep a plan you trust. The new WAIT command gives read-your-writes consistency on standbys.
Two smaller changes are worth knowing. COPY FROM is faster on text and CSV input, COPY TO can now write JSON, and ON_ERROR SET_NULL lets a load continue past bad values. For monitoring, log_lock_waits is now on by default, there is a new pg_stat_lock view, and the wraparound warning now starts at 100 million transactions instead of 40 million.
Checklist Before You Upgrade to PG19
Before you upgrade, check the changed defaults. JIT is now off, max_locks_per_transaction is 128, standard_conforming_strings is always on, and sync_error_count in pg_stat_subscription_stats is now sync_table_error_count, which will break any monitoring built on the old name.
Planning the move? A major version upgrade needs pg_upgrade, dump and restore, or logical replication. For pgEdge Enterprise Postgres, the upgrade steps are in our docs. For a Spock cluster, I have written up both approaches using a 17 to 18 upgrade as the example. The rolling upgrade adds a new node on the new version and retires the old one. The in-place upgrade uses pg_upgrade --link just one node at a time. If you take the in-place route, note that pg_upgrade does not carry over Spock’s replication origins, so you need to recreate them. The post shows how.
Worth knowing: the November 12 update releases for PostgreSQL 18.7, 17.12, 16.16 and 15.20 fixed 52 security vulnerabilities and over 140 bugs. That includes several fixes for incremental backups that could produce corrupt backups, so take a new full backup after updating. PostgreSQL 14 reached end of life at 14.25, so anyone still on it should plan a major version upgrade. During the PostgreSQL 19 release candidates, several fixes also went into REPACK CONCURRENTLY, pg_plan_advice, parallel autovacuum and the automatic enablement of logical replication, so test these on your own workload before relying on them.
Getting the packages. The pgEdge repository requires an access certificate. Install the pgEdge repository package on your host, then register the host with sudo pgedge-subscription-manager register-system. Send the client.csr file it creates to pgEdge support with your organization name and customer ID, and say whether you need a trial or a paid subscription. When the certificate comes back, install it with sudo pgedge-subscription-manager install <path to client.crt>, which also enables the repository. After that you can install PostgreSQL 19 and the supporting components with dnf or apt. The full steps, with Debian and Ubuntu instructions as well, are in the docs.
Further Reading
The PostgreSQL 19 release notes are available for deep insights into what changed and why. However, if you’re looking for a more casual understanding of some of these fundamental changes to the PostgreSQL Project, Shaun Thomas wrote about just about all of these changes already in a “Looking Forward to PostgreSQL 19” series on our blog - browse through and take a look, anytime.


