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 1r8tiW-00CPxL-Ix for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Dec 2023 02:57:25 +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 1r8tiV-004iPk-4A for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Dec 2023 02:57:23 +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 1r8tiU-004iPb-ML for pgsql-hackers@lists.postgresql.org; Fri, 01 Dec 2023 02:57:22 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8tiR-009Szh-U4 for pgsql-hackers@lists.postgresql.org; Fri, 01 Dec 2023 02:57:22 +0000 Received: from [10.10.20.129] (node-pgc.pool-101-109.dynamic.totinternet.net [101.109.128.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: a.lepikhov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id F1C9EE21039; Fri, 1 Dec 2023 05:57:16 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1701399438; bh=NK+yXSUm7iXP+RNDY5UWLJH1D8rkcgGd+x5sn8tMxU8=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=OKsGHjhuMraJjq3/HRX7A68of9NvAlbvWJHwoJudayftm09jWEq02Pal9lFJYJlOg do0jQBN4gqF1Drm0zyImkporIMVddEL1uEd/J+xlTWky4E6h11QC1WrGaD4Qfsnbbp U6J8fYxM7TB5Egc0UKJ4AalTDpFSNkTTI8x4AiXJ3wVuQgxU9zyE39LPwcU/oGi/Zb xcG/iS7Abh50lEY120fhGSqBTsIIJJ/f3bEKaqLDedMi4blx2ahKnHDLa63l+9vb8o oKkm+8YlODFXlv5dlWmUX1O/f/+hkLacR0f6LcXokFZoPGPfXub12Bgpb55Nh7uKvC Tfk9BhB9SWQpA== Message-ID: <79de837a-33c2-481b-91dd-7f3926262baa@postgrespro.ru> Date: Fri, 1 Dec 2023 09:57:13 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Report planning memory in EXPLAIN ANALYZE To: Alvaro Herrera , Ashutosh Bapat Cc: Andy Fan , jian he , David Rowley , PostgreSQL Hackers References: <202311301140.wo7f6eoi772a@alvherre.pgsql> Content-Language: en-US From: Andrei Lepikhov Organization: Postgres Professional In-Reply-To: <202311301140.wo7f6eoi772a@alvherre.pgsql> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 30/11/2023 18:40, Alvaro Herrera wrote: > Well, SUMMARY is enabled by default with ANALYZE, and I'd rather not > have planner memory consumption displayed by default with all EXPLAIN > ANALYZEs. So yeah, I still think this deserves its own option. > > But let's hear others' opinions on this point. I'm only one vote here. I agree; it should be disabled by default. The fact that memory consumption outputs with byte precision (very uncomfortable for perception) is a sign that the primary audience is developers and for debugging purposes. -- regards, Andrei Lepikhov Postgres Professional