Incremental Update: Minor Editorial Feedback on Release Announcement Draft
Two new messages have appeared since the initial solicitation. The thread remains purely administrative with no technical design substance, but there are a few noteworthy editorial exchanges:
Robert Treat's Review (2026-05-11)
Treat provided three pieces of feedback on the draft:
-
Partition pruning wording concern: He flagged that the item "Improve the planner's ability to apply partition pruning to more cases" reads like a feature enhancement rather than a bug fix, which is incongruent with a minor/patch release announcement. He didn't have a concrete rewrite because he hadn't located the underlying commit.
-
Free space map item rewrite: He suggested rewording the free-space-map recovery fix description, proposing to drop the word "tables" as unnecessary clutter, and offered a tighter phrasing. This is a readability/accuracy concern — the original wording could mislead readers about the scope of the fix.
-
Missing security fixes: Treat noted that a "sizeable number of security related fixes" had been committed that day and were absent from the draft, asking whether a v2 incorporating those was forthcoming. This is the most operationally significant observation — it flags that the draft was circulated before the security content was finalized, consistent with the typical pattern where CVE wording is coordinated separately and merged into the announcement late.
Jonathan Katz's Response (2026-05-12)
Katz responded only to the free-space-map item, linking to the specific commit (8e8b2bef7) and indicating he adopted the rewrite. He did not address the partition-pruning wording concern or the missing security fixes in this message, suggesting those are either being handled offline or will appear in a v2 draft.
Assessment
No technical substance has emerged. The exchange is exactly the kind of proofreading/editorial feedback predicted in the prior analysis. The most interesting signal is the confirmation that security-related fixes were still being integrated into the announcement as of May 11, consistent with the tight coordinated-disclosure timeline typical of PostgreSQL minor releases.