model-writtenrun 1422 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- jian he reported that different GROUP BY columns could receive the same query ID because RangeTblEntry.groupexprs was excluded from jumbling in #1, and Tom Lane confirmed that PostgreSQL 14 distinguished those queries in #2.
- Michael Paquier identified the regression as new to PostgreSQL 18 and proposed an exception to query-ID stability for a backpatch in #3; Tom Lane supported that decision and urged inclusion in PostgreSQL 18.2 in #5.
- jian he submitted #6 to include grouping expressions in jumbling and also address collisions between different SELECT lists by including TargetEntry.resjunk, with regression tests for both issues.
- Michael Paquier separated the longstanding resjunk behavior from the recent regression in #7, explaining that any resjunk change could not be backpatched and supplying a GROUP BY-only revision with expanded tests.
- Michael Paquier committed #7 with identical code and test hunks as e217dc7484 and announced its backpatch to PostgreSQL 18 in #8.
- jian he resubmitted the remaining resjunk fix with additional GROUP BY examples in #9; Keisuke Kuroda later discussed test results and the tension between identical execution plans and distinct SELECT lists in #10, leaving that portion under discussion with no landing shown.