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 1u9P11-001P6Q-7V for pgsql-bugs@arkaria.postgresql.org; Mon, 28 Apr 2025 13:59:23 +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 1u9P0y-001DAU-CP for pgsql-bugs@arkaria.postgresql.org; Mon, 28 Apr 2025 13:59:21 +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 1u9P0y-001DAL-43 for pgsql-bugs@lists.postgresql.org; Mon, 28 Apr 2025 13:59:21 +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 1u9P0x-0000o4-1E for pgsql-bugs@lists.postgresql.org; Mon, 28 Apr 2025 13:59:20 +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 53SDxHQC776000; Mon, 28 Apr 2025 09:59:17 -0400 From: Tom Lane To: marcos sicat cc: Pavel Stehule , "pgsql-bugs@lists.postgresql.org" Subject: Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE In-reply-to: References: Comments: In-reply-to marcos sicat message dated "Mon, 28 Apr 2025 13:05:28 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <775998.1745848757.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Apr 2025 09:59:17 -0400 Message-ID: <775999.1745848757@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk marcos sicat writes: > The function is the same between v15 and v17. Is there a subtle differe= nce in performance for nested subqueries in v17? Your next step should be to compare the plans for the function's query. The auto_explain or pg_stat_statements extensions could be used to check that in-situ, if manually EXPLAINing that query doesn't yield insight. regards, tom lane