--- title: "PostgreSQL 18.6, 17.11, 16.15, 15.19, 14.24 and 19 Beta 3 Released!" url: https://daily.dev/posts/postgresql-18-6-17-11-16-15-15-19-14-24-and-19-beta-3-released--qxvmohp6x source_url: https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365 type: article source: "PostgreSQL" published: 2026-08-13T13:12:05.372Z updated: 2026-08-16T05:31:22.171Z tags: ["database", "postgresql"] reading_time: 7 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # PostgreSQL 18.6, 17.11, 16.15, 15.19, 14.24 and 19 Beta 3 Released! **[PostgreSQL](https://daily.dev/sources/postgres)** · 7 min read · 0 upvotes · 0 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions 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._ ## Similar posts on daily.dev - [PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 Released\!](https://daily.dev/posts/postgresql-18-4-17-10-16-14-15-18-and-14-23-released--gahxaz8kn) · PostgreSQL · 11 upvotes · 0 comments - [PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 Released\!](https://daily.dev/posts/postgresql-18-1-17-7-16-11-15-15-14-20-and-13-23-released--wwybaugkn) · PostgreSQL · 22 upvotes · 0 comments - [PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 Released\!](https://daily.dev/posts/postgresql-18-2-17-8-16-12-15-16-and-14-21-released--nnaoaiphj) · PostgreSQL · 7 upvotes · 1 comments --- Tags: [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/postgresql-18-6-17-11-16-15-15-19-14-24-and-19-beta-3-released--qxvmohp6x)