On 8/9/26 3:03 PM, Tom Lane wrote:
"Jonathan S. Katz" <[email protected]> writes:On 8/9/26 2:28 PM, Tom Lane wrote:Contrary to what you say at the top of the list, this doesn't affect v18, only v14-v16. I think this one is definitely important enough to mention, but maybe put it separately from the main list?The list was generated from my build of the v18 release notes, and this was in there - though I found the commit message that did confirm it's only v14-16.That's an artifact of my release note process: the initial draft in the latest stable branch documents everything, then after I copy that text into the older branches I remove anything that's not relevant to the latest branch.
Ah OK, good to know for the future (though there's still a nonzero chance I trip over it should it happen again :)I did remove it in a4c41bbcc, which is why you don't see it anymore.
What do you think of this framing: === This update fixes over 110 bugs that were reported in the last several months. This specific issue only affects PostgreSQL 14, 15, and 16, but we're highlighting it in the release announcement due to its severity:* Fix a self-deadlock that could occur while replaying WAL generated by an older minor version. This regression, introduced in the previous set of minor releases, could cause a standby server following a primary running an older minor version to become stuck.
The remainder of issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL.
... == Thanks, Jonathan
OpenPGP_signature.asc
Description: OpenPGP digital signature
