Re: BUG #18854: PostgreSQL chooses a suboptimal execution plan when using a specific WHERE filter

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