Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW - Mailing list pgsql-bugs

From David Rowley
Subject Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
Date
Msg-id CAApHDvod3V=TKBB=Z3M-bPquzyznR1SYra77NWCTZLUUERm28g@mail.gmail.com
Whole thread
List pgsql-bugs
On Tue, 7 Jul 2026 at 17:11, John Naylor <johncnaylorls@gmail.com> wrote:
> - /* No ORDER BY clause then all rows are peers */
> ...
> + /* No ORDER BY clause and RANGE mode means all rows are peers. */
>
> Was the old comment wrong? Or are all rows still peers, but that's not
> sufficient to show monotonicity?

The test needed to be updated because detecting monotonically
increasing and decreasing in ROWS mode wasn't correct. The comment got
updated along with the test.

David



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #19519: REPACK can fail due to missing chunk for toast value
Next
From: Bharath Rupireddy
Date:
Subject: Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger