Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8Ekt-0008Fb-Cy for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Aug 2020 03:27:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k8Ekq-0003A2-L0 for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Aug 2020 03:27:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8Ekq-00039t-8Q for pgsql-hackers@lists.postgresql.org; Wed, 19 Aug 2020 03:27:12 +0000 Received: from mail-il1-x143.google.com ([2607:f8b0:4864:20::143]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1k8Ekn-0000SY-1O for pgsql-hackers@lists.postgresql.org; Wed, 19 Aug 2020 03:27:11 +0000 Received: by mail-il1-x143.google.com with SMTP id t13so19458083ile.9 for ; Tue, 18 Aug 2020 20:27:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=wYjGh+mVFWHAQPhZFR7MboKrb8SOgmY6kuAGv9SIjP0=; b=jdg+gz6kzryPB/W5vz2E+1dioNIsTygwzWqwDeknUsJmwlizDUJxxRgVFJL9sO7YjO mO4saaRGgo6oJWmeuyvwP6+/Xj1KGj7GsFvnWdxKeN+0UKLRU4EwLfwppU73J55mcLF6 pM4z+XKnNp+Zshf7T9RajmWMsRt+TQS1WU1BIM/r8I79kfJLeZ78TyTnh65YRPrItWPt 7VtDjLzhfsjWRPXGfIixk5CyNM3oYQAnRyY8LWFsxxVuD5uPoOovKjIF9jQtPXFphRkN RlD9UUKtXNL6fpkHLcDImPUE9glgverfZ2jGHrWIpLOj3Xby60KWcZ0eX1w4HC77DLKf tkbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=wYjGh+mVFWHAQPhZFR7MboKrb8SOgmY6kuAGv9SIjP0=; b=l1p2FHwNarR7SZjK+86/nekTE55qYWgoHwfQLkR+P9uGKUKKRKI7n6aXJOGccoSn6G 6AM5eVR5lYqHKb/bRSICN/VATvBxKYC5jLCf8GzJ0/mA5KiijzU/vSGj4J5VC47Zkani BmC/xVP7do8qEX/CQWTpp/ZjsU4/gnMpu75waY5rj6JdTEEU8F0jMFl8Z805oSUSjsoV ZLxnonN0BME2Tqdg9EjPFY5gJnSgxKyzOJDLroqEulAdeUMm2h9bZSF/SYDaXG90ybHh UWsgxwtgMwaZWFYNWQ/IQwJOjAaeohQeYNOPgeHQjqo0CMXBoNBN9otnEEx9HFbw2sHm 44kQ== X-Gm-Message-State: AOAM533BPmvwk4wXLXhklKzGJNn7NV43sU76Lzcq/YEy6NCUXEBp1392 y5ohrj2jXFQIo4TBguzA/JP8BVa9GE5oKw== X-Google-Smtp-Source: ABdhPJzjDPFiz4kaOB13gb4bYC1z/L1eoU2wr3Hf++tv/NY+LoUThWRBbvedCSiyjZTjuJWqe+Ew+A== X-Received: by 2002:a92:de43:: with SMTP id e3mr19571922ilr.124.1597807628068; Tue, 18 Aug 2020 20:27:08 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id j79sm13011369ilg.42.2020.08.18.20.27.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Aug 2020 20:27:07 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 565378003BF; Tue, 18 Aug 2020 22:27:06 -0500 (CDT) Date: Tue, 18 Aug 2020 22:27:06 -0500 From: Justin Pryzby To: Pierre Giraud Cc: pgsql-hackers@lists.postgresql.org, Fujii Masao Subject: Re: [PG13] Planning (time + buffers) data structure in explain plan (format text) Message-ID: <20200819032706.GQ17022@telsasoft.com> References: <07b226e6-fa49-687f-b110-b7c37572f69e@dalibo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <07b226e6-fa49-687f-b110-b7c37572f69e@dalibo.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Aug 07, 2020 at 02:30:01PM +0200, Pierre Giraud wrote: > Hi all, > > As far as I understand, in the upcoming version 13, information about > buffers used during planning is now available in the explain plan. > > […] > Planning Time: 0.203 ms > Buffers: shared hit=14 > […] > > For a matter of consistency, I wonder if it would be possible to format > it like the following: > > […] > Planning: > Planning Time: 0.203 ms > Buffers: shared hit=14 Thanks for reporting. I added this here. https://wiki.postgresql.org/wiki/PostgreSQL_13_Open_Items -- Justin