Changing that parameter had no effect on the version 17 instance. The query itself produces results in a matter of a second or so, but the function still hangs and does not return.
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?
