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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(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 23:49:00
Message-ID: CAApHDvoQ3QF5VRwhkjTOCaJzsNfPQbm7OB6qWBP+PK5DH9WLkw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 18 Nov 2026 at 12:42, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > I had an LLM draft most of that up locally. I'm just wondering if it's
> > worth pursuing or not.
>
> I'd argue not ...

I think I'm pretty much with you there. I didn't think it was worth
too many human cycles to write, and if that's true then offloading a
boatload of machine-generated code just adds future burden to humans.
A problem we're fighting on multiple fronts these days :-(

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2026-11-17 23:54:23 Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY
Previous Message Tom Lane 2026-11-17 23:42:23 Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY