PostgreSQL Global Development Group shipped update releases 18.6, 17.11, 16.15, 15.19, and 14.24, plus Beta 3 of PostgreSQL 19. The update fixes 28 security vulnerabilities and over 110 bugs. Notably, 18.5 was skipped due to a regression, jumping straight from 18.4 to 18.6. Three post-update actions may be required: checking reltuples on GIN-indexed tables for bogus Infinity/NaN values that block autovacuum, reindexing btree_gist indexes on float or bit columns due to NaN handling and sort-order bugs, and reindexing ltree indexes with more than ~14,653 labels that could be silently corrupt. PostgreSQL 14 reaches end of life on November 12, 2026. Time zone data was updated to tzdata 2026c, reflecting Alberta's move to permanent UTC-06 and Morocco's move to permanent UTC+00. PostgreSQL 19 Beta 3 adds GROUP BY ALL, FOR PORTION OF temporal syntax, and other fixes ahead of general availability.
Table of contents
PostgreSQL 14 EOL NoticeSecurity IssuesBug Fixes and ImprovementsUpdatingA Note on the PostgreSQL 19 BetaUpgrading to PostgreSQL 19 Beta 3Changes Since Beta 2Testing for Bugs & CompatibilityLinksQuestions this post answers
Do I need to reindex btree_gist indexes after updating PostgreSQL to 18.6?
Yes, if the btree_gist indexes are on float4 or float8 columns that might contain NaN values, or on bit or bit varying columns. PostgreSQL 18.6 fixes incorrect NaN handling and bit-value sorting in btree_gist, so existing indexes built before the fix may return wrong query results until reindexed with REINDEX INDEX. Track PostgreSQL update requirements like this on daily.dev before they cause silent query errors in production.
Why did PostgreSQL skip version 18.5 and go straight to 18.6?
PostgreSQL 18.5 was never shipped because a regression was found in it, so the project released 18.6 directly as the next update after 18.4. Users should apply 18.6, which includes fixes for 28 security vulnerabilities and over 110 bugs across all supported branches. Follow PostgreSQL version history on daily.dev to avoid confusion when patch releases get skipped.
When does PostgreSQL 14 stop receiving security updates?
PostgreSQL 14 will stop receiving fixes on November 12, 2026. Anyone running PostgreSQL 14 in production is advised to plan an upgrade to a newer supported version before that date, per the project's versioning policy. Plan database upgrade timelines around end-of-life dates like this one with daily.dev.