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 1jR6Tj-0008F2-Ib for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Apr 2020 03:55: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 1jR6Ti-0008Rf-ED for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Apr 2020 03:55:14 +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 1jR6Ti-0008RW-2E for pgsql-hackers@lists.postgresql.org; Wed, 22 Apr 2020 03:55:14 +0000 Received: from mail-qk1-x72c.google.com ([2607:f8b0:4864:20::72c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jR6Tb-0003hA-Ja for pgsql-hackers@postgresql.org; Wed, 22 Apr 2020 03:55:12 +0000 Received: by mail-qk1-x72c.google.com with SMTP id l78so1100354qke.7 for ; Tue, 21 Apr 2020 20:55:07 -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=RGhGu0VHxhrGoSV4Ne89KtK/gnEiv9anBhAhj4HQpWM=; b=P0OGf+5fSa1T+XpNwpdbpg91wvGC4zH0GI3MlkR3gJr4JnvgCpI/fB9xUnkmvt0unU Jr245HieJHD5QJtyqyickBr9b834a8RJfelmL4bsXWFFXsvMCaAQIeUGX5G09dnSUJ/q JVY657HopDC4J+TGzCwUinAVYcCArWfC2VGitIDPOrooAzP/tuHw7f4fiAjfFFeig/R1 sBCQbeVBc4pYOEBEe2db13REHyhsaNgFRM71zclE3ygfmqM0YIuqkHYL8UGf7F2bBGNZ LiMK9eTdkUq/0GQhasGF5DtlqwULOnE4SuBBQDXQUR1G1oHqZl6efoIgKJe6oncvOxzJ OYAg== 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=RGhGu0VHxhrGoSV4Ne89KtK/gnEiv9anBhAhj4HQpWM=; b=ohoggfZ1YZurG2MqZjUd8cVbi6BAPBNux0ruX2dwFDm5HjwI/a3F0IiKrzNv9izynE kzWYgpaQIjp0D8CeyAL0fTGrNGE0pRZjvqbV2/xcX9Mz6DRP7NEUS8OL4kNUIYJ0pLmd /6MPSBRGIOZJcSg18iW0i3fgoEx091dsdR8j2T5Cu7IyiRCJRQQz38aA3nm2c0nMkXJY XTz8ylhFlUw+ibhGYXa/PTQP+1KPMp3unTJga2RD+2W4HssROZ0FzsPiM55SfuGYrmyA VzfA14yLJvdIMqjuxjwje4EpMGsk0SDfO5aevITCoHR1nc1NF/cvMI5p4VvdnXrtHV/D Edhw== X-Gm-Message-State: AGi0PuZtCJWvohY3+qa3Glb/wwq0vp9DczjPNirRDf93Khkr0MmD+6rB JNv1buaOKbt/43/P/TjWVT6BEA== X-Google-Smtp-Source: APiQypLBSZ7b92+tgb5NGIYPENsDgwkP0sANV95qVhbDCxnEIMgNQ1bYeR/h5cbs+JBXz3VEYqUzZA== X-Received: by 2002:a37:9b0a:: with SMTP id d10mr25151057qke.50.1587527704981; Tue, 21 Apr 2020 20:55:04 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id t14sm3265359qtj.71.2020.04.21.20.55.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Apr 2020 20:55:04 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 811F8801457; Tue, 21 Apr 2020 22:55:01 -0500 (CDT) Date: Tue, 21 Apr 2020 22:55:01 -0500 From: Justin Pryzby To: Amit Kapila Cc: Julien Rouhaud , Kyotaro Horiguchi , Peter Eisentraut , Dilip Kumar , Kuntal Ghosh , Fujii Masao , Kirill Bychik , pgsql-hackers , Thomas Munro Subject: Re: WAL usage calculation patch Message-ID: <20200422035501.GN3890@telsasoft.com> References: <20200418204105.GL26953@telsasoft.com> <20200420.164656.881770765734654652.horikyota.ntt@gmail.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 Wed, Apr 22, 2020 at 09:15:08AM +0530, Amit Kapila wrote: > > > > And add the acronym to the docs: > > > > > > > > $ git grep 'full page' '*/explain.sgml' > > > > doc/src/sgml/ref/explain.sgml: number of records, number of full page writes and amount of WAL bytes > > > > > > > > "..full page writes (FPW).." > > > > > > Indeed! Fixed (using lowercase to match current output). > > > > I searched through the documentation and AFAICS most of occurances of > > "full page" are follwed by "image" and full_page_writes is used only > > as the parameter name. > > > > I'm fine with fpw as the acronym, but "fpw means the number of full > > page images" looks odd.. > > > > I don't understand this. Where are we using such a description of fpw? I suggested to add " (FPW)" to the new docs for "explain(wal)" But, the documentation before this commit mostly refers to "full page images". So the implication is that maybe we should use that language (and FPI acronym). The only pre-existing use of "full page writes" seems to be here: $ git grep -iC2 'full page write' origin doc origin:doc/src/sgml/wal.sgml- Internal data structures such as pg_xact, pg_subtrans, pg_multixact, origin:doc/src/sgml/wal.sgml- pg_serial, pg_notify, pg_stat, pg_snapshots are not directly origin:doc/src/sgml/wal.sgml: checksummed, nor are pages protected by full page writes. However, where And we're not using either acronym. -- Justin