Re: unstable query plan on pg 16,17,18

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Attila Soki <atiware(at)gmx(dot)net>
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-24 15:57:04
Message-ID: 0c8b9845-a2ac-4613-8075-45dc55911143@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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.

>
> I could now share some general infos about the query, if you still interested.
Yes, we still have a problem. So, any additional info that can let us
build a repro is appreciated.

--
regards, Andrei Lepikhov,
pgEdge

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Attila Soki 2026-02-24 16:48:15 Re: unstable query plan on pg 16,17,18
Previous Message Attila Soki 2026-02-24 15:50:55 Re: unstable query plan on pg 16,17,18