PostgreSQL 19 removes RADIUS auth, adds password expiration warnings
The upcoming PostgreSQL 19 release drops support for RADIUS authentication, citing its reliance on insecure UDP, and adds a new password_expiration_warning_threshold setting that warns users seven days before their password expires by default. It also warns after successful MD5 password authentication, forces standard_conforming_strings to always be on, and disallows carriage returns and line feeds in database, role, and tablespace names.
GoKawiil's interpretation of the reporting above, not reported fact.
These changes signal PostgreSQL's continued push to close longstanding security gaps, even at the cost of breaking compatibility with older dumps, clusters, or authentication setups. Organizations still relying on RADIUS, MD5 passwords, or non-standard string escaping will need to migrate before upgrading, which could require advance planning for large deployments.
- RADIUS authentication support is being removed entirely due to unfixable UDP-based insecurity.
- Old dumps using standard_conforming_strings = off won't load into PostgreSQL 19 without using updated pg_dump tools.
- New warnings target weak security practices like MD5 passwords and expiring credentials.
Source: postgresql.org, 2026-11-20
Published there as: “PostgreSQL 19”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.