Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
От | Peter Geoghegan |
---|---|
Тема | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
Дата | |
Msg-id | CAH2-Wzkduf6pevzTfGpXr29SoXb9jH6AxAkbJM-cJo1EU0M57Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 (Sajith Prabhakar Shetty <ssajith@blackduck.com>) |
Ответы |
Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
|
Список | pgsql-bugs |
On Thu, Jul 17, 2025 at 11:49 AM Sajith Prabhakar Shetty <ssajith@blackduck.com> wrote: > Thanks for the response, but I don’t understand when you meant “you are using different index”, by any chance did you meanthe 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 schemastructure. 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
В списке pgsql-bugs по дате отправления: