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

From Tom Lane
Subject Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Date
Msg-id 1628600.1749914148@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-bugs
Lowell Hought <lowell.hought@gmail.com> writes:
> Why would it return with a LIMIT clause, but not without the LIMIT clause?

[ shrug... ]  I still suppose this is due to a poor choice of plan
in the no-LIMIT case, but you've yet to provide the info needed
for someone else to reproduce the problem.  You could try comparing
EXPLAIN output in the LIMIT and no-LIMIT cases.

            regards, tom lane



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
Next
From: Tom Lane
Date:
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17