Re: Hashed SAOP on composite type with non-hashable column errors at runtime

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Hashed SAOP on composite type with non-hashable column errors at runtime
Date: 2026-06-05 18:17:21
Message-ID: 3735924.1780683441@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> In the second place, the same hazard exists for range and
> multirange types, which can have non-hashable subtypes.
> AFAICT noplace at all is defending against that.

I meant to attach the test case I'd made to demonstrate
that this is indeed broken. It's a small variant of
your bug-hashed-saop.sql.

regards, tom lane

Attachment Content-Type Size
bug-with-range.sql text/plain 741 bytes

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-06-05 19:11:25 Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
Previous Message Tom Lane 2026-06-05 18:12:02 Re: Hashed SAOP on composite type with non-hashable column errors at runtime