The PostgreSQL Global Development Group has rolled out maintenance releases for 18.6, 17.11, 16.15, 15.19, and 14.24, along with the third beta of PostgreSQL 19. This batch addresses 28 security vulnerabilities and over 110 bugs reported in recent months. Notably, version 18.5 was skipped due to a regression, so upgrades from 18.4 to 18.6 are the direct path.
Here are the key points:
- Security fixes: The update closes CVE-2026-6464, a vulnerability in
psql'sCOPY FROM STDINhandling, plus many other CVEs. Developers usingpsqlfor bulk data loading should review the release notes for full details. - Three upgrade caveats: After updating, you may need additional steps if you use:
- Parallel GIN index builds – ensure your configuration and scripts handle the changes correctly.
- btree_gist extension – check compatibility and re-index if necessary.
- ltree data type – verify behavior and adjust queries or indexes as needed.
- PostgreSQL 14 EOL notice: Support for PostgreSQL 14 ends on November 12, 2026. If you're running 14 in production, start planning your upgrade to a newer version to stay within the support window.
- PostgreSQL 19 Beta 3: The third beta is available for testing, giving you an early look at new features. Beta releases are for evaluation, not production use.
The jump from 18.4 to 18.6 underscores the urgency of these fixes, and the listed caveats highlight potential breaking changes in specific features. For developers, this means:
- Update promptly to protect against known vulnerabilities, especially if you use
psqlwithCOPY. - Review the release notes for the specific bugs fixed and any migration steps.
- Plan for PostgreSQL 14 end-of-life if you haven't already, as it will stop receiving fixes soon.
This release cycle emphasizes the importance of staying current with PostgreSQL minor versions and testing beta versions to prepare for future upgrades. Keep an eye on the official release notes for the complete change log.