| From: | Attila Soki <atiware(at)gmx(dot)net> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: unstable query plan on pg 16,17,18 |
| Date: | 2026-02-24 09:16:08 |
| Message-ID: | 1C445A2F-3256-4F04-B55D-9850581FF39A@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 23 Feb 2026, at 21:25, Andrei Lepikhov <lepihov(at)gmail(dot)com> 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
https://explain.depesz.com/s/eb32
Regards,
Attila
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2026-02-24 11:09:43 | Re: unstable query plan on pg 16,17,18 |
| Previous Message | Andrei Lepikhov | 2026-02-24 09:11:15 | Re: unstable query plan on pg 16,17,18 |