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

From Tom Lane
Subject Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Date
Msg-id 88316.1749351768@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17  (Lowell Hought <lowell.hought@gmail.com>)
Responses Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
List 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 by date:

Previous
From: Lowell Hought
Date:
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Next
From: Lowell Hought
Date:
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17