Re: POC, WIP: OR-clause support for indexes

On 23.11.2023 12:23, Andrei Lepikhov wrote:
> I think the usage of nodeToString for the generation of clause hash is
> too expensive and buggy.
> Also, in the code, you didn't resolve hash collisions. So, I've
> rewritten the patch a bit (see the attachment).
> One more thing: I propose to enable transformation by default at least
> for quick detection of possible issues.
> This code changes tests in many places. But, as I see it, it mostly
> demonstrates the positive effect of the transformation.

On 24.11.2023 06:30, Andrei Lepikhov wrote:

> On 23/11/2023 16:23, Andrei Lepikhov wrote:
>> This code changes tests in many places. But, as I see it, it mostly
>> demonstrates the positive effect of the transformation.
>
> I found out that the postgres_fdw tests were impacted by the feature.
> Fix it, because the patch is on the commitfest and passes buildfarm.
> Taking advantage of this, I suppressed the expression evaluation
> procedure to make regression test changes more clear.

Thank you for your work. You are right, the patch with the current
changes looks better and works more correctly.

To be honest, I didn't think we could use JumbleExpr in this way.

--
Regards,
Alena Rybakina
Postgres Professional