Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate
Date: 2025-04-04 16:03:21
Message-ID: CAPpHfdtJks3MoVnDKtYde7+esU3kgemSuSqEEOiQ4EB5xg0qjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, Apr 4, 2025 at 6:47 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> On Fri, Apr 4, 2025 at 9:17 AM Alexander Korotkov
> <akorotkov(at)postgresql(dot)org> wrote:
> >
> > Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate
> >
> > This commit implements the automatic conversion of 'x IN (VALUES ...)' into
> > ScalarArrayOpExpr. That simplifies the query tree, eliminating the appearance
> > of an unnecessary join.
>
> I haven't looked at this patch, but it seems likely that it is related
> to the recent failures I noticed in CI in the subselect test when the
> regress suite is run by 002_pg_upgrade.pl

Thank you for pointing. I'm looking right now.

------
Regards,
Alexander Korotkov
Supabase

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2025-04-04 16:28:54 pgsql: Further optimize nbtree search scan key comparisons.
Previous Message Tom Lane 2025-04-04 15:57:29 pgsql: Stabilize regression test from c0962a113.

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2025-04-04 16:03:46 Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits
Previous Message Peter Geoghegan 2025-04-04 16:02:51 Re: Replace IN VALUES with ANY in WHERE clauses during optimization