| From: | Attila Soki <atiware(at)gmx(dot)net> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: unstable query plan on pg 16,17,18 |
| Date: | 2026-02-26 16:15:52 |
| Message-ID: | 33A1B02B-1FDD-4F5F-8370-26DA72490009@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 24 Feb 2026, at 17:48, Attila Soki <atiware(at)gmx(dot)net> wrote:
>
>> On 24 Feb 2026, at 16:57, Andrei Lepikhov <lepihov(at)gmail(dot)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 setting join_collapse_limit=7
regards,
Attila
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Attila Soki | 2026-02-26 16:22:47 | Re: unstable query plan on pg 16,17,18 |
| Previous Message | Feike Steenbergen | 2026-02-25 16:35:34 | Re: MERGE INTO... WHEN NOT MATCHED BY SOURCE index usage |