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 1jLUec-0008F9-5e for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2020 16:31:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jLUea-0004wY-F7 for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2020 16:31:16 +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 1jLUea-0004vT-4d for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2020 16:31:16 +0000 Received: from mail-qt1-x842.google.com ([2607:f8b0:4864:20::842]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jLUeX-0001Cm-2H for pgsql-hackers@postgresql.org; Mon, 06 Apr 2020 16:31:14 +0000 Received: by mail-qt1-x842.google.com with SMTP id m33so194362qtb.3 for ; Mon, 06 Apr 2020 09:31:12 -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=MSa5y+JjQbtZIW3nScO4tJdf/bFGh6gsbuZDhMdkPdY=; b=f01IzKlNhjywOZ5xr/+bCVyR8LXvZ4JU7RPbEaa85pp+T03NHGzFiEeIYEZc0vmetZ kImzGOBFt4yssoR8nytRs8U3uCnTKPPbTNlWA2LR0s/eosMOGDEPOrB4Y/vR+VP6vVob aPi2fiqtZZlLSoWV23Qdd8B2nqjZdzHJud34yg6orN5Ma6QmTrPF0NOIbiXyY5nFggYM bU+v9Ji797A0C2D11+n/GDGT8Pj/Doxf3RIBynaDoI5q4sDUnYNLgsNA2t1OjXBvE77T msRvXNGIx1jD/Z2FygPv8F0c9v4BFQxzDb2Iv9vCwDvKdoYRydZ8C94LjV6c57AkGD3W e04g== 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=MSa5y+JjQbtZIW3nScO4tJdf/bFGh6gsbuZDhMdkPdY=; b=AdET+JuA2a9vq+zW/fCWCd/1I017hePQGsedlJRN8v2/Z9wIFe4eoUqh/+GjqbUn+g 5JxyP/NP/BBz0Zrcy9ymDHGi14ugwX1htaEdrD2V+/lKw2Bbjya9E8mAATUwouxIdACB 6m3WsWX1eINDppE67r/ZfAI4uVLOqYLd4R1eCKSrCkPc/cHfSGi2DLEXFOOEiNVrFi5n owq9WDDUmGi8bNuItaM1RNp7X1FwaGuXIwJwmVkBH6OCeW6oetDHMon5/PG80Mqpm8hl 6/JfPVNrgL3GGwwbuN7Ddw+lNevYLbFQqXZ7jAqvBfyduPTGFxoXyeHNQRNphJbSEykF vNaA== X-Gm-Message-State: AGi0PubsYrxrcVR85IAlLPfRbylK0JVmvP0jdCPxgpJct+T117EiYh1r d/dv3CKgsVXSrC4QYIRaFpJtPA== X-Google-Smtp-Source: APiQypJJT8SjqM0O+3EblbfVF1m+es2Y7WhamkebnwxIGikQiSJFv3Zv45iq8D9BmFUJW17UO59ELA== X-Received: by 2002:ac8:5350:: with SMTP id d16mr230882qto.298.1586190672159; Mon, 06 Apr 2020 09:31:12 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id o6sm8523268qkd.113.2020.04.06.09.31.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Apr 2020 09:31:11 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id B79C38007F7; Mon, 6 Apr 2020 11:31:09 -0500 (CDT) Date: Mon, 6 Apr 2020 11:31:09 -0500 From: Justin Pryzby To: Peter Eisentraut Cc: Amit Kapila , Dilip Kumar , Julien Rouhaud , Kuntal Ghosh , Fujii Masao , Kirill Bychik , PostgreSQL Hackers , Thomas Munro Subject: Re: WAL usage calculation patch Message-ID: <20200406163109.GD2228@telsasoft.com> References: <20200402124818.GD64485@nol> 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 Mon, Apr 06, 2020 at 05:01:30PM +0200, Peter Eisentraut wrote: > I noticed in some of the screenshots that were tweeted that for example in > > WAL: records=1 bytes=56 > > there are two spaces between pieces of data. This doesn't match the rest of > the EXPLAIN output. Can that be adjusted? We talked about that here: https://www.postgresql.org/message-id/20200402054120.GC14618%40telsasoft.com -- Justin