Re: Inconsistent Behavior of GROUP BY ROLLUP in v17 vs master

Richard Guo <guofenglinux@gmail.com>

From: Richard Guo <guofenglinux@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: David Rowley <dgrowleyml@gmail.com>, 邱宇航 <iamqyh@gmail.com>, Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2025-10-21T05:26:19Z

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

On Tue, Oct 21, 2025 at 1:18 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Richard Guo <guofenglinux@gmail.com> writes:
> > Oops, I made a mistake in the test case for v18.  Fixing it now…

> Bleah.  I pretty much don't ever commit things into back branches
> without running regression tests there as well as in master.
> Postgres is a moving target.

Indeed.  I should have always stayed alert to the possibility that
test outputs might differ across branches, even for simple queries.
But somehow, it slipped through this time.

I just pushed a fix to v18 and am now staring at the buildfarm
nervously.  Fingers crossed this time.

- Richard