Re: BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples. - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples.
Date
Msg-id CABUevEy-GF37G3euD822xGBAyO+dHxBE-AeMxi_yshgPMpuM9Q@mail.gmail.com
Whole thread Raw
In response to BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples.  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Wed, Jul 26, 2023 at 1:07 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference:      18036
> Logged by:          Patrick Leamon
> Email address:      patrick@redbubble.com
> PostgreSQL version: 14.3
> Operating system:   Unsure - AWS Aurora PostgreSQL
> Description:
>
> Hi,
>   I'm hitting some odd query plans.  The structure of the query is like
> this:
>
> SELECT field1, field2, field3
> FROM my_table
> WHERE (field1, field2) IN (("a", "b"), ("c", "b"))

...

What do you get if you try this query on PostgreSQL?

--
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/



pgsql-bugs by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Next
From: Christophe Pettus
Date:
Subject: Documentation bug at: current/sql-vacuum.html, Notes