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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: 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-16 20:16:55
Message-ID: CAApHDvopH5k71pnX035q5dRcm-BcEAKe8499mMJmWbbQaJuUYQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 17 Nov 2026 at 05:29, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2026-11-16 12:26:36 +0100, Tor Erik Linnerud wrote:
> > Likely cause: in llvmjit_expr.c, EEOP_HASHDATUM_NEXT32 combines the hash
> > function's full 64-bit Datum. hash_range returns its hash via
> > PG_RETURN_INT32, which sign-extends, and the next column's rotate then
> > shifts those upper bits into the combined hash, wiping it. The interpreter
> > truncates to 32 bits and is not affected.
>
> That's obviously a bug. Presumably in
>
> 2024-08-20 adf97c15623 Speed up Hash Join by making ExprStates support hashing
>
> CCing David.

Thanks. Looking at this now.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Борис Мурашов 2026-11-16 20:23:02 Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
Previous Message Robert Haas 2026-11-16 20:16:46 Re: BUG #19908: pg_upgrade --check crashes instance if running in a different PID Namespace then the old cluster