Re: Inconsistent Behavior of GROUP BY ROLLUP in v17 vs master
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Richard Guo <guofenglinux@gmail.com>, 邱宇航 <iamqyh@gmail.com>, Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2025-09-25T03:24:07Z
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
David Rowley <dgrowleyml@gmail.com> writes: > On Thu, 25 Sept 2025 at 13:01, Richard Guo <guofenglinux@gmail.com> wrote: >> I plan to push this patch soon, unless there are any objections. > What's your confidence levels on the logic now being correct? 100%? > 90%? Hopeful? FWIW, my confidence in it is rather low. I've not had time to think this through carefully, but it seems to me that the test ought to involve whether there is an empty grouping set, yet the proposed patch does no such thing --- or at least, if it manages to achieve that effect, it's not obvious how. 18.1 will not be coming out till November, so I feel no need to rush to judgment on what to do here. regards, tom lane