Hi,Please see the proposed draft of the 2026-02-12 announcement. Please review for errors, typos, notable omissions, etc.
I also wanted to ensure I captured the correct set of post-upgrade steps for the `ltree` issue. I tried to simplify it as much as possible while trying to convey how narrow the scope of having to reindex. However, if I. misunderstood, please help me correct.
Thanks, Jonathan
The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 18.2, 17.8, 16.12, 15.16, and 14.21. This release fixes over 65 bugs reported over the last several months. For the full list of changes, please review the [release notes](https://www.postgresql.org/docs/release/). Bug Fixes and Improvements -------------------------- This update fixes over 65 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL. * Fix inconsistent case-insensitive text matching in the `ltree` extension. If you use an index on an `ltree` column, in some cases you may need perform a reindex. See the "Updating" section for additional instructions. * Executing `ALTER TABLE ... ADD CONSTRAINT` to add a `NOT NULL` constraint on a column that already is marked as `NOT NULL` now requires the constraint name to match the existing constraint name. * Fix trigger behavior when `MERGE` is executed from a `WITH` query to include rows affected by the `MERGE`. * Several query planner fixes. * Fix for text substring search for non-deterministic collations. * Several fixes for `NOTIFY` error handling and reporting. * Use the correct ordering function in GIN index parallel builds. * Fix incorrect handling of incremental backups with tables larger than 1GB. * Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record. * Fix for `ALTER PUBLICATION` to ensure event triggers contain all set options. * Several fixes around replication slot initialization. * Don't advance replication slot after a logical replication parallel worker apply failure to prevent transaction loss on the subscriber. * Fix error reporting for SQL/JSON path type mismatches. * Fix JIT compilation function inlining when using LLVM 17 or later. * Add new server parameter `file_extend_method` to control use of `posix_fallocate()`. * Fix `psql` tab completion for the `VACUUM` command options. * Fix `pg_dump` to handle concurrent sequence drops gracefully and to fail if the calling user explicitly lacks privileges to read the sequence. * Several fixes for `amcheck` around `btree` inspection. * Avoid crash in `pg_stat_statements` when an `IN` list contains both constants and non-constant expressions. This release also updates time zone data files to tzdata release 2025c, which only has a historical data change for pre-1976 timestamps in Baja California. Updating -------- All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use `pg_upgrade` in order to apply this update release; you may simply shutdown PostgreSQL and update its binaries. If you have indexes on `ltree` columns and do not use the `libc` collation provider, after upgrading to the latest version, you must reindex any `ltree` column. You can use `REINDEX INDEX CONCURRENTLY` to minimize the impact on your system. Users who have skipped one or more update releases may need to run additional post-update steps; please see the release notes from earlier versions for details. For more details, please see the [release notes](https://www.postgresql.org/docs/release/). Links ----- * [Download](https://www.postgresql.org/download/) * [Release Notes](https://www.postgresql.org/docs/release/) * [Security](https://www.postgresql.org/support/security/) * [Versioning Policy](https://www.postgresql.org/support/versioning/) * [Submit a Bug](https://www.postgresql.org/account/submitbug/) * [Donate](https://www.postgresql.org/about/donate/) If you have corrections or suggestions for this release announcement, please send them to the [email protected]_ public [mailing list](https://www.postgresql.org/list/).
OpenPGP_signature.asc
Description: OpenPGP digital signature
