From: Andrei Lepikhov <lepihov@gmail.com>
To: yonisade83@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18854: PostgreSQL chooses a suboptimal execution plan when using a specific WHERE filter
Date: Tue, 18 Mar 2025 15:16:36 +0100
Message-ID: <91d297ae-71ca-4406-a404-f8daa0b0c4a5@gmail.com> (raw)
In-Reply-To: <18854-f5bc660117569bdf@postgresql.org>
References: <18854-f5bc660117569bdf@postgresql.org>
On 3/18/25 12:34, PG Bug reporting form wrote:
> Query has a specific WHERE filter for tiny lookup table "t8" (19 rows) which
> generates an execution plan which has two "Nested Loop" steps instead of
> "Hash Join" steps which makes the query finish after 90 seconds (and spiking
> the server CPU when being ran by dozens of sessions simultaneously) instead
> of ~3 seconds (when commenting out that specific WHERE filter clause I
> mentioned below):
May you provide EXPLAIN ANALYZE VERBOSE in standard text output format?
--
regards, Andrei Lepikhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: lepihov@gmail.com, yonisade83@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18854: PostgreSQL chooses a suboptimal execution plan when using a specific WHERE filter
In-Reply-To: <91d297ae-71ca-4406-a404-f8daa0b0c4a5@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox