From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lowell Hought <lowell.hought@gmail.com>
cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not
 return in Postgresql 17
In-reply-to: <75D714EA-CD1E-4F80-A2E8-29E378EC2200@gmail.com>
References: <e9eb5136fb60188fc61c110e9706709fc13638e0.camel@cybertec.at>
 <75D714EA-CD1E-4F80-A2E8-29E378EC2200@gmail.com>
Comments: In-reply-to Lowell Hought <lowell.hought@gmail.com>
	message dated "Sat, 07 Jun 2025 20:40:32 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <81945.1749348479.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 07 Jun 2025 22:07:59 -0400
Message-ID: <81946.1749348479@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/81946.1749348479%40sss.pgh.pa.us>
Precedence: bulk

Lowell Hought <lowell.hought@gmail.com> writes:
> If I run the query outside of the function it works as expected.  But th=
e 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 =3D force_custom_plan" before running the
function?

			regards, tom lane