The PostgreSQL Global Development Group is planning for an out-of-cycle release on November 21, 2024 to address two regressions that were released as part of the [November 14, 2024 update release](https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/), which included releases for [17.1, 16.5, 15.9, 14.14, 13.19, and 12.21](https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/). As part of this release, we will issue fixes for all supported versions (17.2, 16.6, 15.10, 14.15, 13.20), and for 12.22, even though PostgreSQL 12 is now EOL.
While these regressions may not impact all users, the PostgreSQL Global Development Group determined that it would be better to address these sooner than the [next scheduled release on February 13, 2025](https://www.postgresql.org/developer/roadmap/). A high-level description of the regressions are as follows. 1. The fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/) [prevented `ALTER USER ... SET ROLE ...` from having any effect](https://www.postgresql.org/message-id/CADOZwSb0UsEr4_UTFXC5k7%3DfyyK8uKXekucd%2B-uuGjJsGBfxgw%40mail.gmail.com). This will be fixed in the upcoming release. 2. Certain PostgreSQL extensions took a dependency on an Application Build Interface (ABI) that was modified in this release and [caused them to break](https://www.postgresql.org/message-id/CABOikdNmVBC1LL6pY26dyxAS2f%2BgLZvTsNt%3D2XbcyG7WxXVBBQ%40mail.gmail.com). Currently, this can be mitigated by rebuilding the extensions against the updated definition. If you are impacted by either of these issues, we advise to wait for the availability of 17.2, 16.6, 15.10, 14.15, 13.20, and 12.22 before upgrading.
