Re: unstable query plan on pg 16,17,18
Attila Soki <atiware@gmx.net>
From: Attila Soki <atiware@gmx.net>
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: pgsql-performance@postgresql.org,
Laurenz Albe <laurenz.albe@cybertec.at>
Date: 2026-02-26T16:15:52Z
Lists: 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 setting join_collapse_limit=7 regards, Attila