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 1silC8-0091i7-OP for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 01:40:28 +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 1silC6-0007k2-QK for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 01:40:27 +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 1silC6-0007jR-F0 for pgsql-general@lists.postgresql.org; Tue, 27 Aug 2024 01:40:27 +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.94.2) (envelope-from ) id 1silC4-001bv6-Hr for pgsql-general@lists.postgresql.org; Tue, 27 Aug 2024 01:40:25 +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 47R1eD5g2962670; Mon, 26 Aug 2024 21:40:13 -0400 From: Tom Lane To: nikhil raj cc: "pgsql-generallists.postgresql.org" , NIKITA PATEL , Patel Khushbu Subject: Re: Significant Execution Time Difference Between PG13.14 and PG16.4 for Query on information_schema Tables. In-reply-to: References: Comments: In-reply-to nikhil raj message dated "Tue, 27 Aug 2024 03:19:04 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2962668.1724722813.1@sss.pgh.pa.us> Date: Mon, 26 Aug 2024 21:40:13 -0400 Message-ID: <2962669.1724722813@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk nikhil raj writes: > I've encountered a noticeable difference in execution time and query > execution plan row counts between PostgreSQL 13 and PostgreSQL 16 when > running a query on information_schema tables. Surprisingly, PostgreSQL 16 > is performing slower than PostgreSQL 13. Yeah, it looks like that condition on "table_name" is not getting pushed down to the scan level anymore. I'm not sure why not, but will look closer tomorrow. regards, tom lane