Re: Hashed IN only applied to first encountered IN - Mailing list pgsql-hackers

From David Rowley
Subject Re: Hashed IN only applied to first encountered IN
Date
Msg-id CAApHDvqSFcGvyYVJZAk7BW544cd4KY3B9KofnjkCdpV49hwVGg@mail.gmail.com
Whole thread Raw
In response to Re: Hashed IN only applied to first encountered IN  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Hashed IN only applied to first encountered IN
List pgsql-hackers
On Wed, 2 Apr 2025 at 01:31, David Rowley <dgrowleyml@gmail.com> wrote:
>
> On Wed, 2 Apr 2025 at 00:51, David Geier <geidav.pg@gmail.com> wrote:
> > The hashed IN optimization is only applied to the first encountered
> > ScalarArrayOpExpr during the expression tree traversal in
> > convert_saop_to_hashed_saop_walker(). Reason being that the walker
> > returns true which aborts the traversal.
>
> > I've also attached a patch with a fix.
>
> Thanks for the report and fix.  On first inspection your patch looks
> fine.  I'll have a closer look tomorrow.

I've now pushed and backpatched the relevant portion of this back to v14.

Thanks again.

David



pgsql-hackers by date:

Previous
From: Shayon Mukherjee
Date:
Subject: Re: Proposal to Enable/Disable Index using ALTER INDEX (with patch)
Next
From: Peter Geoghegan
Date:
Subject: Re: Adding skip scan (including MDAM style range skip scan) to nbtree