Re: unstable query plan on pg 16,17,18 - Mailing list pgsql-performance

From Attila Soki
Subject Re: unstable query plan on pg 16,17,18
Date
Msg-id 33A1B02B-1FDD-4F5F-8370-26DA72490009@gmx.net
Whole thread Raw
In response to Re: unstable query plan on pg 16,17,18  (Attila Soki <atiware@gmx.net>)
Responses Re: unstable query plan on pg 16,17,18
List pgsql-performance
On 24 Feb 2026, at 17:48, Attila Soki <atiware@gmx.net> wrote:
>
>> On 24 Feb 2026, at 16:57, Andrei Lepikhov <lepihov@gmail.com> wrote:
>>
>> On 24/2/26 16:50, Attila Soki wrote:
>>> Now with join_collapse_limit=7 works for me and I am not able to flip the plan. makes that sense?
>>
>> It is almost a game of chance. But if it solves your problem - why not ;)?
>>
>>> should I still test with increased statistic on table_k.dp_end_dat as Laurenz suggested?
>>
>> Yes, it may provide us additional info for developing.
> ok i try that and come with more info.
> Should I set join_collapse_limit back to default for this test?
>

Increasing the statistics of dp_end_dat did not helped. With statistic 1000 I was not able to get a good plan without
settingjoin_collapse_limit=7 

regards,
Attila


pgsql-performance by date:

Previous
From: Feike Steenbergen
Date:
Subject: Re: MERGE INTO... WHEN NOT MATCHED BY SOURCE index usage
Next
From: Attila Soki
Date:
Subject: Re: unstable query plan on pg 16,17,18