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 1ui0lG-006cQ6-RI for pgsql-bugs@arkaria.postgresql.org; Sat, 02 Aug 2025 01:10:11 +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 1ui0lF-00AP7Y-O1 for pgsql-bugs@arkaria.postgresql.org; Sat, 02 Aug 2025 01:10:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ui0lF-00AP7P-Fl for pgsql-bugs@lists.postgresql.org; Sat, 02 Aug 2025 01:10:09 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ui0lC-000IWi-2U for pgsql-bugs@lists.postgresql.org; Sat, 02 Aug 2025 01:10:08 +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 57219xYo2532877; Fri, 1 Aug 2025 21:10:00 -0400 From: Tom Lane To: Peter Geoghegan cc: Sajith Prabhakar Shetty , Andrei Lepikhov , "pgsql-bugs@lists.postgresql.org" , Todd Cook Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 In-reply-to: References: <2a8243eb-a8e8-4c2d-9c46-7152782d84f8@gmail.com> <2121299.1753993453@sss.pgh.pa.us> <2128451.1753997128@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Fri, 01 Aug 2025 17:47:21 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2532875.1754096999.1@sss.pgh.pa.us> Date: Fri, 01 Aug 2025 21:09:59 -0400 Message-ID: <2532876.1754096999@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > My inclination is to pursue the simpler approach, and just accept the > remaining performance shortfall. This is a rare enough case that I > think that that'll be acceptable. But input on how to make this > trade-off would be helpful. My thought here is that there is not a lot you can do in v17: it's been out for a year and we dare not destabilize it. Take the easy near-guaranteed win and be happy. Additional improvements can be pursued at our leisure in the master branch. regards, tom lane