Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uQSbs-00BQOl-93 for pgsql-bugs@arkaria.postgresql.org; Sat, 14 Jun 2025 15:15:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uQSbq-008zqs-5R for pgsql-bugs@arkaria.postgresql.org; Sat, 14 Jun 2025 15:15:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uQSbp-008zqj-TD for pgsql-bugs@lists.postgresql.org; Sat, 14 Jun 2025 15:15:54 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uQSbo-001yYL-28 for pgsql-bugs@lists.postgresql.org; Sat, 14 Jun 2025 15:15:53 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 55EFFmoj1628601; Sat, 14 Jun 2025 11:15:48 -0400 From: Tom Lane To: Lowell Hought cc: Laurenz Albe , 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: References: <75D714EA-CD1E-4F80-A2E8-29E378EC2200@gmail.com> <81946.1749348479@sss.pgh.pa.us> <89144.1749352271@sss.pgh.pa.us> <90964.1749353175@sss.pgh.pa.us> Comments: In-reply-to Lowell Hought message dated "Sat, 14 Jun 2025 09:27:19 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1628599.1749914148.1@sss.pgh.pa.us> Date: Sat, 14 Jun 2025 11:15:48 -0400 Message-ID: <1628600.1749914148@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Lowell Hought 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