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 1jKF92-0008OC-Qx for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Apr 2020 05:45:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jKF8V-0002i9-7I for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Apr 2020 05:44:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jKF8V-0002i1-0M for pgsql-hackers@lists.postgresql.org; Fri, 03 Apr 2020 05:44:59 +0000 Received: from mail-qv1-xf29.google.com ([2607:f8b0:4864:20::f29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jKF8S-0002lS-DR for pgsql-hackers@lists.postgresql.org; Fri, 03 Apr 2020 05:44:58 +0000 Received: by mail-qv1-xf29.google.com with SMTP id bu9so3017500qvb.13 for ; Thu, 02 Apr 2020 22:44:55 -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:in-reply-to:user-agent; bh=GIHCS/mcPDaeKHJiU2Qu67f1Zqh3nezPogrPgk1ATfg=; b=K3VdGn6udC1j7vLrPca66RIlSOCLOFDu9C0wgzjbGLKmSWBGybzB3f6QLFUpa+/Qmu O72I9Ht4yWDNPo2oBgkFCop609at+Tjvix8vhiqXDb936B99o1b7eQ4Jn3Rh533NHYfx 3sPSBYsCMCUFc3jYAUgVUBVK80Jdf6OXV/BCDNQ0JP987r2KTPve+2yP0dTZp2RCf1U1 tllmpZV/AfZTk/mqAu76hYBR/Zs3BJnMJWgg/7o4/K0Qp5/Jt8WN6AWK8M+4N0OcsB35 XFZXkeM+EurM4zcohgVTdk/JKGd1mEeWs9/MtrFWPJY9iXGCrXt/H+x09R//nryA6NbQ 7ATw== 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:in-reply-to:user-agent; bh=GIHCS/mcPDaeKHJiU2Qu67f1Zqh3nezPogrPgk1ATfg=; b=BZcnyhAE1B0LFoxuG74eZFkhIwabec7WbqoaSl0vFa+3SKvYWrtyz5xCrwfhJqeLZv JWKWDDzvJxQyx23KDD1TR1eDmgWQ0iRD2/R/lHoMyBDu+x3bvc3yCD8OVXcLHGOvSJ3L qNVEzuSw/66VqghzXWNsCJQi0pYNd+laVbVJ/GX2RHvvzLLjPDMnhx+mYA5kx76BxXDw WzoEOSgj9P54uSrCi5BqTKGbfdx7tbdpL3leBusDzrbu95DWe+/BeCrsRmQrUuvQhP5O opQUTMyq4CH+EUZgJXRoTCcimyRPpMsyxaDrkWagcdUZUOP/eyoTRvf/zak2J1PzV5OO CPVQ== X-Gm-Message-State: AGi0PuY5JJiFC+4XSteuHWHdCgld0AkI30dad5PCjFpfQW8vK6FY3dh1 ATsjEB61ez/YLrbgwyNx6whWkA== X-Google-Smtp-Source: APiQypK8gCDsQ3M3rXYdnPYhRTqbLrSRWgfELcX1aAyOTVlabZqZSYlOa5utLO+VwV9RWDyeBguqRA== X-Received: by 2002:a05:6214:174f:: with SMTP id dc15mr6903492qvb.107.1585892694550; Thu, 02 Apr 2020 22:44:54 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id f21sm5654587qtc.97.2020.04.02.22.44.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2020 22:44:53 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id EC67B80092E; Fri, 3 Apr 2020 00:44:51 -0500 (CDT) Date: Fri, 3 Apr 2020 00:44:51 -0500 From: Justin Pryzby To: Amit Kapila Cc: Kyotaro Horiguchi , PostgreSQL Hackers , Julien Rouhaud , Dilip Kumar , Kirill Bychik , Fujii Masao Subject: Re: User Interface for WAL usage data Message-ID: <20200403054451.GN14618@telsasoft.com> References: <20200402054120.GC14618@telsasoft.com> <20200402.145826.78549992113208057.horikyota.ntt@gmail.com> <20200402063540.GE14618@telsasoft.com> <20200403051111.GM14618@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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, Apr 03, 2020 at 10:52:02AM +0530, Amit Kapila wrote: > On Fri, Apr 3, 2020 at 10:41 AM Justin Pryzby wrote: > > > > > > > > > > WAL: records=2359 full page records=42 bytes=447788 > > > > 1) records; 2) pages ("full page images"); 3) bytes > > > > That is exactly like sort (method/type/size) and hash (buckets/batches/size), > > and *not* like buffers, which shows various values all in units of "pages". > > > > The way you have written (2) appears to bit awkward. I would prefer > "full page writes" or "full page images". I didn't mean it to be the description used in the patch or anywhere else, just the list of units. I wonder if it should use colons instead of equals ? As in: | WAL: Records: 2359 Full Page Images: 42 Size: 437kB Note, that has: 1) two spaces; 2) capitalized "fields"; 3) size rather than "bytes". That's similar to Buckets: | Buckets: 1024 Batches: 1 Memory Usage: 44kB I'm not sure if it should say "WAL: " or "WAL ", or perhaps "WAL: " If there's no colon, then it looks like the first field is "WAL Records", but then "size" isn't as tightly associated with WAL. It could say: | WAL Records: n Full Page Images: n WAL Size: nkB For comparison, buffers uses "equals" for the case showing multiple "fields", which are all in units of pages: | Buffers: shared hit=15 read=2006 Also, for now, the output can be in kB, but I think in the future we should take a recent suggestion from Andres to make an ExplainPropertyBytes() which handles conversion to and display of a reasonable unit. -- Justin