Re: Inconsistent Behavior of GROUP BY ROLLUP in v17 vs master
邱宇航 <iamqyh@gmail.com>
From: 邱宇航 <iamqyh@gmail.com>
To: David Rowley <dgrowleyml@gmail.com>,
Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2025-09-23T12:26:40Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix test case from 40c242830
- ee49f2cf447a 18.1 landed
-
Fix pushdown of degenerate HAVING clauses
- 40c2428307b8 18.1 landed
- 18d261409348 19 (unreleased) landed
-
Allow pushdown of HAVING clauses with grouping sets
- 67a54b9e83d3 18.0 cited
-
Mark expressions nullable by grouping sets
- f5050f795aea 18.0 cited
> 2025年9月23日 15:38,David Rowley <dgrowleyml@gmail.com> 写道: > > If you check the release notes and the commit message for f5050f795 > you'll see that it does mention that wrong results could be returned. > > What wasn't mentioned was that this wasn't fixed in prior versions. > The reason being is that the fix required changing the query tree > representation, which we can't change in the back branches due to > incompatibility with stored rules in existing databases. So, a change > in query results for certain queries here is expected. Yeah, I got it. Thanks David and Bruce. And what about the query 2. This is caused by another commit, and it's not mentioned in the commit message or the mailing discussion. Best regards, Yuhang Qiu