The copyleft Redis fork announced on 17 November 2026 that it will get no further releases; its author recommends moving to Valkey and says to avoid returning to Redis.
PostgreSQL 19 drops RADIUS and changes defaults that can block upgrades
EditorialBy 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
- PostgreSQL: Release 19 release notes, 19 November 2026
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.
You may be interested in
An attacker used a compromised GitHub account and leaked credentials for four weeks, copying customer contacts, contract terms, SQL editor text and encrypted API keys. PingCAP says the databases themselves were not reached.
Packages for those minor releases, including PostgreSQL 18, move to the YUM archive and get no further updates; servers on RHEL, Rocky Linux or AlmaLinux 10.0 or 9.6 should move to a newer minor release.
From 28 September 2026 Cloud SQL’s Viewer, Reader and legacy Viewer roles no longer carry the export permission, so exports using them fail. Cloud Service Mesh’s ISTIOD control planes on GKE are deprecated, with support ending on 1 March 2028.
Synology advisory SA-26:21 of 19 November 2026 rates CVE-2026-120382 in the DSM and BeeStation OS OAuth API critical (CVSS 9.8); DSM 7.4.1-90080-2 and 7.3.2-86009-6 were scheduled by 20 November, and other branches have no fix yet.
No workaround exists, and a second advisory published the same minute lists 25 more DSM flaws, with fixes named only for the two newest release lines.
Any Plex Media Server reachable from the internet on 1.43.2 or earlier should be treated as suspect. QNAP says a clean reinstall and new credentials are needed, not only the update.
Fixes exist only for the 11.9, 12.0 and 12.1 lines, so owners of older object stores face a migration rather than a patch. No exploitation had been reported at publication.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More DataBaseThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.