Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Lowell Hought <lowell.hought@gmail.com>
From: Lowell Hought <lowell.hought@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-bugs@lists.postgresql.org
Date: 2025-06-08T02:57:27Z
Lists: pgsql-bugs
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? Lowell On Sat, Jun 7, 2025 at 9:08 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Lowell Hought <lowell.hought@gmail.com> writes: > > If I run the query outside of the function it works as expected. But > the function never returns. > > This isn't that surprising either: a query inside a function is > often translated into a "generic" plan that doesn't depend on > specific parameter values, typically sacrificing runtime to > avoid repeated planning. Does it get any better if you do > "set plan_cache_mode = force_custom_plan" before running the > function? > > regards, tom lane >