E.5. Release 17.2
Prev | Up | Appendix E. Release Notes | Home | Next

## E.5. Release 17.2 #

Release date: 2024-11-21

This release contains a few fixes from 17.1. For information about new features in major release 17, see Section E.7.

### E.5.1. Migration to Version 17.2 #

A dump/restore is not required for those running 17.X.

However, if you are upgrading from a version earlier than 17.1, see Section E.6.

### E.5.2. Changes #

- Repair ABI break for extensions that work with struct `ResultRelInfo` (Tom Lane) §

  Last week's minor releases unintentionally broke binary compatibility with timescaledb and several other extensions. Restore the affected structure to its previous size, so that such extensions need not be rebuilt.

- Restore functionality of `ALTER {ROLE|DATABASE} SET role` (Tom Lane, Noah Misch) §

  The fix for CVE-2024-10978 accidentally caused settings for `role` to not be applied if they come from non-interactive sources, including previous `ALTER {ROLE|DATABASE}` commands and the `PGOPTIONS` environment variable.

- Fix cases where a logical replication slot's `restart_lsn` could go backwards (Masahiko Sawada) §

  Previously, restarting logical replication could sometimes cause the slot's restart point to be recomputed as an older value than had previously been advertised in `pg_replication_slots`. This is bad, since for example WAL files might have been removed on the basis of the later `restart_lsn` value, in which case replication would fail to restart.

- Avoid deleting still-needed WAL files during pg_rewind (Polina Bungina, Alexander Kukushkin) §

  Previously, in unlucky cases, it was possible for pg_rewind to remove important WAL files from the rewound demoted primary. In particular this happens if those files have been marked for archival (i.e., their `.ready` files were created) but not yet archived. Then the newly promoted node no longer has such files because of them having been recycled, but likely they are needed for recovery in the demoted node. If pg_rewind removes them, recovery is not possible anymore.

- Fix race conditions associated with dropping shared statistics entries (Kyotaro Horiguchi, Michael Paquier) §

  These bugs could lead to loss of statistics data, assertion failures, or “can only drop stats once” errors.

- Count index scans in `contrib/bloom` indexes in the statistics views, such as the `pg_stat_user_indexes`.`idx_scan` counter (Masahiro Ikeda) §

- Fix crash when checking to see if an index's opclass options have changed (Alexander Korotkov) §

  Some forms of `ALTER TABLE` would fail if the table has an index with non-default operator class options.

- Avoid assertion failure caused by disconnected NFA sub-graphs in regular expression parsing (Tom Lane) §

  This bug does not appear to have any visible consequences in non-assert builds.

Prev | Up | Next
E.4. Release 17.3 | Home | E.6. Release 17.1