| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | patrick(at)redbubble(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples. |
| Date: | 2023-07-26 11:08:51 |
| Message-ID: | CABUevEy-GF37G3euD822xGBAyO+dHxBE-AeMxi_yshgPMpuM9Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jul 26, 2023 at 1:07 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 18036
> Logged by: Patrick Leamon
> Email address: patrick(at)redbubble(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2023-07-26 17:39:41 | Documentation bug at: current/sql-vacuum.html, Notes |
| Previous Message | Kyotaro Horiguchi | 2023-07-26 08:36:00 | Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used |