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 <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1rT7Kq-000YmR-B8
	for pgsql-performance@arkaria.postgresql.org; Thu, 25 Jan 2024 21:32:32 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1rT7Kp-004b66-JM
	for pgsql-performance@arkaria.postgresql.org; Thu, 25 Jan 2024 21:32:31 +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 <tgl@sss.pgh.pa.us>)
	id 1rT7Kp-004b2D-7z
	for pgsql-performance@lists.postgresql.org; Thu, 25 Jan 2024 21:32:31 +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 <tgl@sss.pgh.pa.us>)
	id 1rT7Km-003MiE-PM
	for pgsql-performance@lists.postgresql.org; Thu, 25 Jan 2024 21:32:30 +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 40PLWR3M456127;
	Thu, 25 Jan 2024 16:32:27 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
cc: Jean-Christophe Boggio <postgresql@thefreecat.org>,
        pgsql-performance@lists.postgresql.org
Subject: Re: I don't understand that EXPLAIN PLAN timings
In-reply-to: 
 <CAApHDvqoP04PS3g6+Wc4LvMEcvbre+iRiVmyph1U2jVJtTJBng@mail.gmail.com>
References: <61e642df-5f48-4e4e-b4c3-58936f90ddaa@thefreecat.org>
 <7c265c1a-2b87-4dc6-8d83-8c7d98e11a2c@thefreecat.org>
 <CAApHDvqX2qTihLG2K4OqzeRneg3h+bwdgL000SjYHPFKiU7eAA@mail.gmail.com>
 <0f1acdd6-1d6a-44bc-80a1-fde4c55c5263@thefreecat.org>
 <CAApHDvqoP04PS3g6+Wc4LvMEcvbre+iRiVmyph1U2jVJtTJBng@mail.gmail.com>
Comments: In-reply-to David Rowley <dgrowleyml@gmail.com>
	message dated "Fri, 26 Jan 2024 10:11:46 +1300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <456125.1706218347.1@sss.pgh.pa.us>
Date: Thu, 25 Jan 2024 16:32:27 -0500
Message-ID: <456126.1706218347@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: 
 <https://www.postgresql.org/message-id/456126.1706218347%40sss.pgh.pa.us>
Precedence: bulk

David Rowley <dgrowleyml@gmail.com> writes:
> I do wonder now if it was a bad idea to make Memoize build the hash
> table on plan startup rather than delaying that until we fetch the
> first tuple. I see Hash Join only builds its table during executor
> run.

Ouch!  If it really does that, yes it's a bad idea.

			regards, tom lane