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 1rTT1X-003EPY-TR for pgsql-hackers@arkaria.postgresql.org; Fri, 26 Jan 2024 20:42: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 1rTT1X-002E8p-2c for pgsql-hackers@arkaria.postgresql.org; Fri, 26 Jan 2024 20:42:03 +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 1rTT1W-002E8h-P4 for pgsql-hackers@lists.postgresql.org; Fri, 26 Jan 2024 20:42:02 +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.94.2) (envelope-from ) id 1rTT1U-003sjH-Gr for pgsql-hackers@postgresql.org; Fri, 26 Jan 2024 20:42:02 +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 40QKfw6s1035226; Fri, 26 Jan 2024 15:41:58 -0500 From: Tom Lane To: David Rowley cc: Richard Guo , PostgreSQL-development Subject: Re: A performance issue with Memoize In-reply-to: References: <422277.1706207562@sss.pgh.pa.us> Comments: In-reply-to David Rowley message dated "Fri, 26 Jan 2024 16:23:46 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1035224.1706301718.1@sss.pgh.pa.us> Date: Fri, 26 Jan 2024 15:41:58 -0500 Message-ID: <1035225.1706301718@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: > I've adjusted the comments to what you mentioned and also leaned out > the pretty expensive test case to something that'll run much faster > and pushed the result. drongo and fairywren are consistently failing the test case added by this commit. I'm not quite sure why the behavior of Memoize would be platform-specific when we're dealing with integers, but ... regards, tom lane