PostgreSQL’s November 2026 update provides versions 18.7, 17.12, 16.16, 15.20, and 14.25, alongside the second release candidate of version 19. The maintenance releases address 52 security vulnerabilities and more than 140 reported bugs. The security fixes cover serious risks including flaws that could let attackers execute arbitrary code, inject SQL, write to unintended files, bypass access controls, or expose server memory. PostgreSQL 14.25 is the final release for version 14: that branch is end-of-life and will receive no further security or bug fixes, so production users should plan an upgrade.
The bug fixes address data integrity, correctness, and reliability across indexes, backups, query planning, partitioning, replication, and SQL features. Some GIN, pg_trgm GiST, TOAST, and bpchar indexes may require reindexing after installation; the release also recommends taking a fresh full backup before continuing incremental backups. Administrators should check for and repair affected NOT NULL constraints on partitioned tables. Other significant corrections prevent corrupted or incomplete backups, missed rows or incorrect query results, crash-related data loss, and replication errors. The update also changes join-removal planning to avoid recurring problems. Because several fixes require follow-up maintenance, upgrading involves more than installing new binaries: administrators should review the release notes and complete the applicable post-update steps.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.