Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Tor Erik Linnerud <tel(at)jklm(dot)no>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
Date: 2026-11-17 14:49:34
Message-ID: 326861.1794926974@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> writes:
> Should we be adding a test case for this? Basically comparing
> HashAgg / multi-batch HashJoin output order with jit on/off.

That's not gonna work on BF animals without JIT.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-11-17 14:57:39 BUG #19912: MERGE NOT MATCHED BY SOURCE sees stale source values after concurrent update (EPQ)
Previous Message PG Bug reporting form 2026-11-17 13:18:49 BUG #19911: Window aggregate over ROWS n FOLLOWING: "unexpected end of tuplestore" after spill