Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org, Peter Eisentraut <peter@eisentraut.org>
Date: 2026-06-05T18:17:21Z
Lists: pgsql-bugs

Attachments

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

Commits

  1. Fix missed checks for hashability of container-type equality.