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 1rCkTd-00H5uB-51 for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Dec 2023 17:53:57 +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 1rCkTb-00FrbR-Rk for pgsql-hackers@arkaria.postgresql.org; Mon, 11 Dec 2023 17:53:55 +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 1rCkTb-00FrbJ-I5 for pgsql-hackers@lists.postgresql.org; Mon, 11 Dec 2023 17:53:55 +0000 Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rCkTY-00BQT7-PD for pgsql-hackers@lists.postgresql.org; Mon, 11 Dec 2023 17:53:54 +0000 Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-77f552d4179so188569385a.1 for ; Mon, 11 Dec 2023 09:53:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702317231; x=1702922031; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=xG/0eVIT23zLJW8kgqxG14TgFlqbVV1Xr6LSkRIc1ak=; b=i5Szk/L6aB7LvHT8IPgJDXFQ81mo89Q1S72vUPLdO0kXd0n42SyoR0oJFjp0rv1nzO XETC7MFKrsOLLZbZZNKa9tqKp1+Ni/cWmd/WEAicU/s0bZFp9Q3bfRiQYQ6x7tfkODwt LJHo/82lxAxhoGBLuUbrNqq7qEhndI+cQxnpWKv94aXmbb+HfCIaJMfdwbvCSid8IY7Q iSfTdy7Z7gE0OLXizIkWeCNOU7pjjL0ySjFpYWzMeHIFMbpqlYMtOWiAnTB+HwTSKwa4 VXmb37/gDVo6NREwAVOUQ64u+Fe/ViKVbfoVGbnH8Hy6G/WdIDRy56wIZcaOctDn3c1s 1PDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702317231; x=1702922031; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=xG/0eVIT23zLJW8kgqxG14TgFlqbVV1Xr6LSkRIc1ak=; b=GR2+qMMqvubLWHHWDGik25gEIcLiu8GJVROPq6WXQ1uvExUuAqPAkPKHP1XFxhxZmY xEzXe+gPXg/gS4hJ7M9sAWZ7XfwPxs0hO2RRxrPM6IVFv1rxvNMjtuvJnpBdbTkTqrsq IuC0Ma4JqHgv13jbDmO1Nywa9VwYkywhRiEVkAfb3fUGhcH14KknqrjxQdNb/NiH6MHA +NTgCbtHWGp17bR3dnaE62NYhRY9JzlGqdXPik6Zk9L3cVEVhhM36vxLE2+eB3SRpJSS t/SwShm5lm2SjjpD5tvUd8KtNRSdMcFNEyNbPrxZpZJO2cZWC3hMXg/dRBzKyr7oFugD rB/g== X-Gm-Message-State: AOJu0YxeFUt/BACEdM5XdGQiztf22Iso8UKXApvaaeBDOMcllBSkOHtC ERjFA2RBHeqqA+hAQlk8UWQnIE1qBTkevIHzirrmHClvXhA= X-Google-Smtp-Source: AGHT+IEZpc8JgggNMaUtdaFZ+o4hL3QulSspZXlDIVbSvPz+ylaVvCGRiypyBwLDY/sVc6CBNWclSlMumFnm4azWd0Q= X-Received: by 2002:a05:6122:12d5:b0:4b2:c554:ef07 with SMTP id d21-20020a05612212d500b004b2c554ef07mr2384354vkp.25.1702301743599; Mon, 11 Dec 2023 05:35:43 -0800 (PST) MIME-Version: 1.0 References: <202311301140.wo7f6eoi772a@alvherre.pgsql> <79de837a-33c2-481b-91dd-7f3926262baa@postgrespro.ru> In-Reply-To: From: Ashutosh Bapat Date: Mon, 11 Dec 2023 19:05:32 +0530 Message-ID: Subject: Re: Report planning memory in EXPLAIN ANALYZE To: jian he Cc: Andrei Lepikhov , Alvaro Herrera , Andy Fan , David Rowley , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Dec 11, 2023 at 2:06=E2=80=AFPM jian he wrote: > > On Mon, Dec 4, 2023 at 3:24=E2=80=AFPM Ashutosh Bapat > wrote: > > > > On Fri, Dec 1, 2023 at 8:27=E2=80=AFAM Andrei Lepikhov > > wrote: > > > > > > On 30/11/2023 18:40, Alvaro Herrera wrote: > > > > Well, SUMMARY is enabled by default with ANALYZE, and I'd rather no= t > > > > have planner memory consumption displayed by default with all EXPLA= IN > > > > 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 h= ere. > > > > > > 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. > > > > That's 2 vs 1. Here's patch with MEMORY option added. Replying to > > Alvaro's earlier relevant comments. > > > > "Include information on planner's memory consumption. Specially, > include the total memory allocated by the planner and net memory that > remains used at the end of the planning. It defaults to > FALSE. > " > doc/src/sgml/ref/explain.sgml > I can view MemoryContextSizeDifference, figure out the meaning. > > But I am not sure "net memory that remains used at the end of the > planning" is the correct description. > (I am not native english speaker). The word "net" is used as an adjective, see [1] [1] https://www.merriam-webster.com/dictionary/net (as an adjective) Does that help? Do you have any other wording proposal? --=20 Best Wishes, Ashutosh Bapat