Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Дата
Msg-id 88316.1749351768@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17  (Lowell Hought <lowell.hought@gmail.com>)
Ответы Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Список pgsql-bugs
Lowell Hought <lowell.hought@gmail.com> writes:
> Yes!  I just changed the parameter as  you suggested and the query returned
> as expected.
> So I guess something changed between version 16 and version 17?  Perhaps
> the default for that setting?

No, that default has not changed.  What apparently happened is that
cost estimates or something changed enough to persuade the planner
to use a generic plan that's considerably inferior to what it was
choosing before.  There's nowhere near enough info in your report
to pin it down more closely than that.

Just to eliminate the obvious --- you did run ANALYZE after the
upgrade, right?  If you had any nondefault settings of
default_statistics_target or similar planner parameters,
did you make sure they got transferred to the new installation?

            regards, tom lane



В списке pgsql-bugs по дате отправления: