| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Sajith Prabhakar Shetty <ssajith(at)blackduck(dot)com> |
| Cc: | Andrei Lepikhov <lepihov(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
| Date: | 2025-07-17 15:55:18 |
| Message-ID: | CAH2-Wzkduf6pevzTfGpXr29SoXb9jH6AxAkbJM-cJo1EU0M57Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jul 17, 2025 at 11:49 AM Sajith Prabhakar Shetty
<ssajith(at)blackduck(dot)com> wrote:
> Thanks for the response, but I don’t understand when you meant “you are using different index”, by any chance did you mean the optimizer?
> Because I have used exactly the same data dump for all PG15,16 and 17 for my tests with no difference in data nor schema structure.
I simply mean that the plan is substantially different, in that there
is an index scan node on 17 that uses a completely different index to
the corresponding index scan node on 15. While the plan looks almost
the same, this one detail is huge.
In other words, I disagree with your summary of the plan, when you
said "Explain plan of the two queries almost same, all the joins and
paths used are exactly same". The paths are not the same.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2025-07-18 09:19:14 | Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution |
| Previous Message | Sajith Prabhakar Shetty | 2025-07-17 15:49:39 | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |