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 1tzPo3-001hvU-SI for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Apr 2025 00:48:44 +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 1tzPo2-00ER03-8r for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Apr 2025 00:48:42 +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 1tzPo1-00EQxG-UO for pgsql-hackers@lists.postgresql.org; Tue, 01 Apr 2025 00:48:41 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tzPnz-002Eoz-3A for pgsql-hackers@lists.postgresql.org; Tue, 01 Apr 2025 00:48:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=CiWNSMz3tmU8l1KRxcNq6aEhNXfOux6qL3zpsgIbkzw=; b=TSVOiOqme/apCt8XbM6S0l0/Iz lQAq879qaLAVPYwnscubqMms0v/lJ4/kd5Q0gfnZKOmx3sDb+ILudQFgT7k+JrQvwbNWu2TBX961K +DLxVM1KYa4pIfuhReVr8/ZWQF8/mQUM9+GRY6/YwBPpcui661pw8+UVhiZ7fMQoyUwX0LiGeSDsI fp5+qMb/VyBV9bb/Rj90XQ6fkaTmW39PKo22JuHEHbsADFXd/cY4tOmwT4V5SeY70aq62r8M/K42X a+pG0hocJDcagCm9+7mZay7YetIwpv5abAWcViT8idydOfpfTXacL+CbmagAcIOCXne2w5KF0pjrF ajBbfkfQ==; Received: from [2409:11:4120:300:2096:b35d:b3f6:8780] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (Exim 4.96) (envelope-from ) id 1tzPnt-008aYf-3A; Tue, 01 Apr 2025 00:48:36 +0000 Date: Tue, 01 Apr 2025 09:48:24 +0900 (JST) Message-Id: <20250401.094824.1077317221843812276.ishii@postgresql.org> To: dgrowleyml@gmail.com Cc: myon@debian.org, pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Add memory/disk usage for Window aggregate nodes in EXPLAIN. From: Tatsuo Ishii In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:2096:b35d:b3f6:8780 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk From: David Rowley Subject: Re: pgsql: Add memory/disk usage for Window aggregate nodes in EXPLAIN. Date: Tue, 1 Apr 2025 11:09:11 +1300 Message-ID: > On Tue, 1 Apr 2025 at 09:40, Christoph Berg wrote: >> =# explain (analyze,buffers off,costs off) select sum(n) over() from generate_series(1,2048) a(n); >> QUERY PLAN >> ────────────────────────────────────────────────────────────────────────────────────────── >> WindowAgg (actual time=2.073..2.686 rows=2048.00 loops=1) >> Window: w1 AS () >> Storage: Disk Maximum Storage: 65kB > > Thank you for testing that. I've just pushed a patch to bump it up to 2500. > > I suspect the buildfarm didn't catch this due to the tuplestore > consuming enough memory in MEMORY_CONTEXT_CHECKING builds. David, Christoph, Thank you for fixing this! -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp