| From: | Lowell Hought <lowell(dot)hought(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 02:57:27 |
| Message-ID: | CAJtAGPpa4yYS6LLO5RHzwe9q7NpHiuuvEX1wVtErpie3EBWZJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Lowell Hought <lowell(dot)hought(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lowell Hought | 2025-06-08 02:59:39 | Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 |
| Previous Message | Michael Paquier | 2025-06-08 02:39:44 | Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements |