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 1sj5lE-00EQO4-2J for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Aug 2024 23:38:04 +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 1sj5lA-00EJBo-D7 for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Aug 2024 23:38:00 +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 1sj5lA-00EJBf-38 for pgsql-hackers@lists.postgresql.org; Tue, 27 Aug 2024 23:38:00 +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 1sj5l8-001l62-4O for pgsql-hackers@lists.postgresql.org; Tue, 27 Aug 2024 23:37:59 +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 47RNbu5X3159018; Tue, 27 Aug 2024 19:37:56 -0400 From: Tom Lane cc: David Rowley , Richard Guo , nikhil raj , pgsql-hackers@lists.postgresql.org Subject: Re: Significant Execution Time Difference Between PG13.14 and PG16.4 for Query on information_schema Tables. In-reply-to: <3156371.1724800521@sss.pgh.pa.us> References: <2962669.1724722813@sss.pgh.pa.us> <2965760.1724724227@sss.pgh.pa.us> <3104695.1724775341@sss.pgh.pa.us> <3147330.1724795532@sss.pgh.pa.us> <3156371.1724800521@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Tue, 27 Aug 2024 19:15:21 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3159016.1724801876.1@sss.pgh.pa.us> Date: Tue, 27 Aug 2024 19:37:56 -0400 Message-ID: <3159017.1724801876@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > That seems like a pretty fishy way to do it. Are you saying that > Memoize is never applicable if there aren't outer joins in the > query? Without OJs there probably won't be any PHVs. Oh, scratch that, I see you mean this is an additional way to do it not the only way to do it. But I'm confused why it works for t1.two+1 AS c1 but not t1.two+t2.two AS c1 Those ought to look pretty much the same for this purpose. regards, tom lane