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 1jRVda-0002EO-T1 for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2020 06:47:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jRVdZ-0004mE-PJ for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2020 06:47:05 +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 1jRVdY-0004m7-K6 for pgsql-hackers@lists.postgresql.org; Thu, 23 Apr 2020 06:47:05 +0000 Received: from wforward3-smtp.messagingengine.com ([64.147.123.22]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jRVdU-0000Rv-C6 for pgsql-hackers@postgresql.org; Thu, 23 Apr 2020 06:47:04 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id BDD89621; Thu, 23 Apr 2020 02:46:54 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 23 Apr 2020 02:46:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=BLPKi0wh1w5VIsWb5kL1roiSlTzd18Nw1tbtVic9D rY=; b=mvQmVv2IxIxbolF8OBIzSdC4q9xuIzF2eiuP4Rq7Ubjp3MPRKzaLLBGCP F9eKWTrIJUEE4cCeg6gv2qG8hpdwG3XbB6374tYjp1KOY48OM+yg0E9+TPgrfFdd dTDnpBxDIs6Q/izF1MlOsBxBdYUfybOJ2XaoIlIClqnikp2k4UCAORkLuvFmT9rp E6z4yP2amZsqClgchefFOO5+zgQdpOhDN+l07/9wFUD5Qx/PEXIb45ebdAbwbW/z raQRvZhcwgCMCNEdvtl/dd4n4UFeFgy5pmDQRgdwtWw2QRODZUHe1MisnMecpT+9 h5L9dfp3h7EyMRVrDSWG1OL3ZGi/Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeekgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgt ohhmnecukfhppeelfedrvdegfedriedrvdegudenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvdhn ughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5df306f1.dip0.t-ipconnect.de [93.243.6.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 11A6C3065D12; Thu, 23 Apr 2020 02:46:51 -0400 (EDT) Subject: Re: WAL usage calculation patch To: Julien Rouhaud , Amit Kapila References: <20200418204105.GL26953@telsasoft.com> <20200420.164656.881770765734654652.horikyota.ntt@gmail.com> <20200422035501.GN3890@telsasoft.com> Cc: Justin Pryzby , Kyotaro Horiguchi , Dilip Kumar , Kuntal Ghosh , Fujii Masao , Kirill Bychik , pgsql-hackers , Thomas Munro From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <05bdb944-e12b-232a-41c0-e78cc9e63d17@2ndquadrant.com> Date: Thu, 23 Apr 2020 08:46:50 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-04-23 07:31, Julien Rouhaud wrote: > I agree that full page writes can be used in this case, but I'm > wondering if that can be misleading for some reader which might e.g. > confuse with the full_page_writes GUC. And as Justin pointed out, the > documentation for now usually mentions "full page image(s)" in such > cases. ISTM that in the context of this patch, "full-page image" is correct. A "full-page write" is what you do to a table or index page when you are recovering a full-page image. The internal symbol for the WAL record is XLOG_FPI and xlogdesc.c prints it as "FPI". -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services