MIME-Version: 1.0
References: <E1u0guq-002dS9-1m@gemulon.postgresql.org>
 <CAAKRu_bFn5xis9gugrnU3N8O6NN8WYncv5NedHfv3J65m_RZ8w@mail.gmail.com>
In-Reply-To: 
 <CAAKRu_bFn5xis9gugrnU3N8O6NN8WYncv5NedHfv3J65m_RZ8w@mail.gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
Date: Fri, 4 Apr 2025 19:03:21 +0300
Message-ID: 
 <CAPpHfdtJks3MoVnDKtYde7+esU3kgemSuSqEEOiQ4EB5xg0qjw@mail.gmail.com>
Subject: Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then
 appropriate
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: Alexander Korotkov <akorotkov@postgresql.org>,
 pgsql-committers@lists.postgresql.org,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAPpHfdtJks3MoVnDKtYde7%2BesU3kgemSuSqEEOiQ4EB5xg0qjw%40mail.gmail.com>
Precedence: bulk

On Fri, Apr 4, 2025 at 6:47=E2=80=AFPM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> On Fri, Apr 4, 2025 at 9:17=E2=80=AFAM Alexander Korotkov
> <akorotkov@postgresql.org> wrote:
> >
> > Convert 'x IN (VALUES ...)' to 'x =3D ANY ...' then appropriate
> >
> > This commit implements the automatic conversion of 'x IN (VALUES ...)' =
into
> > ScalarArrayOpExpr.  That simplifies the query tree, eliminating the app=
earance
> > 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