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

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, 邱宇航 <iamqyh(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inconsistent Behavior of GROUP BY ROLLUP in v17 vs master
Date: 2025-10-21 05:26:19
Message-ID: CAMbWs49QXqkeNWviJNAz5HWg78sNFqRj8Ek-9mXJbKZE3NxU-g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 21, 2025 at 1:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Richard Guo <guofenglinux(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-10-21 05:27:41 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Previous Message Pavel Stehule 2025-10-21 05:10:10 Re: Eliminating SPI / SQL from some RI triggers - take 3