public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrei Lepikhov <[email protected]>
To: Attila Soki <[email protected]>
Cc: [email protected]
Cc: Laurenz Albe <[email protected]>
Subject: Re: unstable query plan on pg 16,17,18
Date: Tue, 24 Feb 2026 12:09:43 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On 24/2/26 10:16, Attila Soki wrote:
> On 23 Feb 2026, at 21:25, Andrei Lepikhov <[email protected]> wrote:
>> Thanks. But I meant your 'good' plan built by the PG14. I think a new
>> feature invented later has added some problems.
>>
>> Current conjecture is the following. As I see, the main problem is
>> with Right Hash Join:
>> -> Hash Right Join (cost=210369.25..210370.30 rows=8 width=99)
>> Its inner side (Hash table) is rebuilt multiple times (around 1k) due
>> to an external parameter (gauf_1.id) in the subtree. It looks like a
>> disaster, and before I thought we don't build hash tables over
>> parameterised query trees at all.
>>
>> So, let me discover a little more, but your PG14 explain could add
>> more details here.
>
> Sorry, I misunderstood that.
> here is the pg14.4 explain
This update gives us more useful details. In PG14, the join search
problem involved at most 9 relations. In PG19, the maximum is now 18
joins. Do you know what your join_collapse_limit is set to? It looks
like subplan pull-ups have made things more complex.
First, we should look into any possible 'rescan cost' issues on our side
as developers.
On your end, please check the join_collapse_limit setting. If needed,
try increasing it to around 20. This might help.
--
regards, Andrei Lepikhov,
pgEdge
view thread (25+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: unstable query plan on pg 16,17,18
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox