Skip to content
TrustList
News

PostgreSQL 19 drops RADIUS and changes defaults that can block upgrades

Editorial

By TrustList Editorial

PostgreSQL 19 adds REPACK CONCURRENTLY and logical replication without a restart, removes RADIUS authentication, warns on MD5 passwords, turns JIT off by default and refuses some clusters at pg_upgrade.

About PostgreSQL 19 drops RADIUS and changes defaults that can block upgrades

PostgreSQL 19 drops RADIUS and changes defaults that can block upgrades

19 November 2026: The PostgreSQL Global Development Group has released PostgreSQL 19, the next major version of the open-source database. Alongside new features for maintenance, replication and query planning, the release notes list a set of incompatibilities that operators need to read before they move: one authentication method is gone, another now warns, several defaults change, and pg_upgrade will refuse some clusters outright.

Not yet independently verified. This rests on the PostgreSQL Global Development Group's own release notes for version 19, dated 19 November 2026 and read on 20 November. We summarise the overview and the incompatibilities section, not every change listed, and have not tested an upgrade ourselves. We will update this when it can be confirmed, and remove this note.

What is new

The headline feature is a new REPACK command that reclaims disk space and reorganises table contents. REPACK (CONCURRENTLY) does this without blocking reads and writes to the table. Other additions named in the overview:

  • pg_plan_advice, an extension for controlling query planner decisions, and pg_stash_advice, which applies plan advice automatically based on the query.
  • Logical replication without a restart: it can now be enabled while wal_level is set to replica, and sequence values are replicated too.
  • A WAIT command for read-your-writes consistency on standby servers.
  • Autovacuum changes: parallel vacuuming of table indexes and prioritisation through a new scoring system.
  • Performance work, including automatic scaling of the number of I/O worker processes and quicker foreign-key checks.

Authentication: RADIUS removed, MD5 warns

RADIUS support has been removed. The project says PostgreSQL only supported RADIUS over UDP, which it calls unfixably insecure, so any pg_hba.conf entry using it must move to another method before the upgrade. MD5 passwords, deprecated in PostgreSQL 18, now trigger a warning after each successful sign-in; it can be turned off with the md5_password_warnings setting. A new setting, password_expiration_warning_threshold, warns users that their password is about to expire, by default seven days ahead.

Changes that can stop an upgrade

  • standard_conforming_strings is always on. Dumps made by pg_dump or pg_dumpall from versions before 19 with the setting off will not load properly. Make dumps with the version 19 tools, or with the setting on.
  • No carriage returns or line feeds in names. Database, role and tablespace names containing them are no longer allowed, and pg_upgrade will not upgrade clusters that use them.
  • inet and cidr indexes. The default index operator class for these types changes from btree_gist to GiST because the btree_gist versions can exclude rows that should be returned. pg_upgrade will refuse clusters with btree_gist inet or cidr indexes.

Defaults that change behaviour

JIT compilation is now off by default, because the cost estimates that switched it on were found to be unreliable; sites running many large analytical queries need to enable it themselves. The default for max_locks_per_transaction rises from 64 to 128 and lock allocation has changed, so custom values need doubling to keep the same capacity. The io_workers setting is replaced by four new settings.

Check before you schedule the move

As with every major release, moving data needs a dump and restore with pg_dumpall, pg_upgrade or logical replication. Before planning a window, search pg_hba.conf for radius entries, list roles still on MD5 passwords, look for btree_gist indexes on inet or cidr columns and for names with line breaks, and note whether your old dumps were made with standard_conforming_strings off. Teams with heavy reporting workloads should benchmark with JIT on and off, and anyone who raised max_locks_per_transaction should recalculate it.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in