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 1jJsba-0007r8-1Z for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Apr 2020 05:41:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jJsbY-0007To-Nl for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Apr 2020 05:41:28 +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 1jJsbY-0007Th-Ca for pgsql-hackers@lists.postgresql.org; Thu, 02 Apr 2020 05:41:28 +0000 Received: from mail-qt1-x82f.google.com ([2607:f8b0:4864:20::82f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jJsbU-0007Ac-Vh for pgsql-hackers@lists.postgresql.org; Thu, 02 Apr 2020 05:41:27 +0000 Received: by mail-qt1-x82f.google.com with SMTP id f20so2335575qtq.6 for ; Wed, 01 Apr 2020 22:41:24 -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=k0OPWTb+NAzvKo2EutftmXEmMxNl9VaEFrAeLQvXOkI=; b=CMQDu1n9CVMhOGEI1DOtZ2YZbECMNYpKBXeInd3xNgiSkGhMDZIQ7au7pcOoqDIf2u 6IrtxtTKvbgf19dNyKdPh0MUFRB9Z+lFckcmS7aoMKu6FdG7vtyU5L0Ihita9g4V0nLh Xm4fSA3VUnrEkY3tnHqOGLhYKFfJgI18LHT+xu6BKvBQ+NLx3tgNki1MeFEV+6efuBma 3P7dVX73r2eMzpARrzfdFHDJTOQS5/nUChiwGBIjOUV8PojrFCHCdJ12i6n3qeWXoiEf 0iIQG8EicXvxMVI9mUSpr2Fx2yjTOfkGWngFovZ0sS9KqUYSMBr6EXxxl/JhrQJId7ar aCeA== 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=k0OPWTb+NAzvKo2EutftmXEmMxNl9VaEFrAeLQvXOkI=; b=trDb+z4RsPkbokMhfe2wrHRnSe8jmdb18LMkVGnfTmqdHZjQBzF/q2mOIycyl9x8gd lGMFmv6p3SGLoGhRrCjYdjRu7/uGswREqBEDpRP5utcJITZ00Wq3WM2dJtN17+PjATcy /tiBYM53lfg3ffTq5uG8VcQvjFcLwx6Pg5fwKrMZwtE1DoNG8GK/sPl22hq3eg/6OPER xa07Bt/Jz44sXSdgferCt+47PQEDos8rF+D0RgVpVY1UlFMhkQrosJDzsBChRL4d6+Aa 1YtTQvgsUBXIy5lzbIzTJn5msfZOnyuiRNN79L2I77+LBYjGrbk4HZRITOPk0snIPHG2 m76Q== X-Gm-Message-State: AGi0PuZyR9UHG2QRtovC4dCFaacUupzBKIWTQu5+hGSe+vgOLb6Uoums WI2N8NIlT0aytypA3QMyH2/CkQ== X-Google-Smtp-Source: APiQypLHkW2ud0fdFasgkiV7MXUT84D1otASzVBMqlLYRvHETwAR0xq1LGEq+DkkGKjRN7LGeSB6Og== X-Received: by 2002:ac8:7288:: with SMTP id v8mr1265327qto.31.1585806083140; Wed, 01 Apr 2020 22:41:23 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id d141sm2827529qke.68.2020.04.01.22.41.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Apr 2020 22:41:22 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id C1E15800755; Thu, 2 Apr 2020 00:41:20 -0500 (CDT) Date: Thu, 2 Apr 2020 00:41:20 -0500 From: Justin Pryzby To: Amit Kapila Cc: PostgreSQL Hackers , Julien Rouhaud , Dilip Kumar , Kirill Bychik , Fujii Masao Subject: Re: User Interface for WAL usage data Message-ID: <20200402054120.GC14618@telsasoft.com> References: 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 Thu, Apr 02, 2020 at 10:13:18AM +0530, Amit Kapila wrote: > In thread [1], we are discussing to expose WAL usage data for each > statement in a way quite similar to how we expose BufferUsage data. > The way it exposes seems reasonable to me and no one else raises any > objection. It could be that it appears fine to others who have > reviewed the patch but I thought it would be a good idea to write a > separate email just for its UI and see if anybody has objection. +1 Regarding v10-0004-Add-option-to-report-WAL-usage-in-EXPLAIN-and-au.patch: I think there should be additional spaces before "full" and before "bytes": > WAL: records=2359 full page records=42 bytes=447788 Compare with these: "Sort Method: %s %s: %ldkB\n", "Buckets: %d (originally %d) Batches: %d (originally %d) Memory Usage: %ldkB\n", "Buckets: %d Batches: %d Memory Usage: %ldkB\n", Otherwise "records=2359 full page records=42" is hard to parse. > Exposed via auto_explain > WAL: records=200 full page records=2 bytes=37387 Same In v10-0002: + * BufferUsage and WalUsage during executing maintenance command can be should say "during execution of a maintenance command". I'm afraid that'll cause merge conflicts for you :( In 0003: + /* Provide WAL update data to the instrumentation */ Remove "data" ?? -- Justin