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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lowell Hought <lowell(dot)hought(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Date: 2025-06-08 03:11:11
Message-ID: 89144.1749352271@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Lowell Hought <lowell(dot)hought(at)gmail(dot)com> writes:
> 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.

Darn. But I'm still pretty sure that the problem is an undesirable
change of plan, and that we don't have enough information to say
more than that. Any chance you could extract a self-contained
test case?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Lowell Hought 2025-06-08 03:16:54 Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Previous Message Lowell Hought 2025-06-08 03:08:06 Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17