Horton
Menu

Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators

cca5507 <cca5507@qq.com>

View thread
From: cca5507 <cca5507@qq.com>
To: Chengpeng Yan <chengpeng_yan@outlook.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: David Rowley <dgrowleyml@gmail.com>
Date: 2026-04-17T12:45:57Z
Lists: pgsql-hackers

Attachments

Hi Chengpeng,

Thanks for your report. After reading the code, I find that there is still
an issue even if the LHS is not null and the comparator is strict (make
myinteq always return null, see the attached sql for details).

The main reason is that we did not consider whether the comparator's
return value is null during looking up the hash. Not sure whether this
is a big problem.

--
Regards,
ChangAo Chen

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix incorrect logic for hashed IN / NOT IN with non-strict operators