Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g3AAz-0001u1-RE for pgsql-committers@arkaria.postgresql.org; Fri, 21 Sep 2018 01:24:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g3AAx-00020W-HL for pgsql-committers@arkaria.postgresql.org; Fri, 21 Sep 2018 01:24:07 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g3AAw-0001zc-Kk for pgsql-committers@lists.postgresql.org; Fri, 21 Sep 2018 01:24:07 +0000 Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g3AAn-0000IW-TY for pgsql-committers@postgresql.org; Fri, 21 Sep 2018 01:24:05 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 82A6D36D7; Thu, 20 Sep 2018 21:23:56 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 20 Sep 2018 21:23:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=4ozBI8lS7jnXpHRc+GDaA3u1Vjj+PUFQdCh0AEVSGXE=; b=ZlM2ODX6 KTAZ3rVz0bH7lDCSZyt9SeAabs02xJqV9yYOqIRPlZLNSRdBXPTYEDyUQZPypWqa MrFeLcB3/TvWFa7/wNfb4i5O/xxFqUVCYAAKrvmAnoYi9R9XXfaper5QSeYgUNwS Pj7xRqYSwgiSoPH2Kq62sGXgu7Ru+wPyrLZX7zQbr4U0NGmuqfKK5B83SilC8m60 oPehKGBvo5EtrnOT5Uc8UEzmGXsMjXxF+wi4UcPeXxyxwcqsEVlJeK+Y7s0G6wSm 5iJz5fDYnxojSv3XpCaUiBed4HN8QYZwxIC4rt3V4e9Ejsg2yhJkH+2p4ZXL0FTU GlaZDe8PX11N/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=4ozBI8lS7jnXpHRc+GDaA3u1Vjj+P UFQdCh0AEVSGXE=; b=PK33UxLLoGwTDq1sJALHuwglsmE39kH1zyYoekaR1ials eZdET9p/NLQbwkYOMkl/Wf6orcyuVKqGBegJ1690m88onKLY81xPWuJe35Eat/5O /0QBy1EbLE8FFz/5bjR924tqoYY25ohyup4XKt/PeKpizeqHxQn24kxGWamyxmeR CATD9T8Ua5UIFmkVTBOD4b2lTu9qSy7jlnoEC0tGIQ8GUY08e+EXFRnsMyS3IgoI WdzyZyVbCnyWySCuAM5VQ/r0z6B9FbQIONfiuu04J3nmN2ObnfLhMerVE4//moRP GMO9DDSwUjuh6pEJcRKHIMcv5573kMxeOWrB0sV7Q== X-ME-Proxy: X-ME-Sender: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 61E43E447F; Thu, 20 Sep 2018 21:23:55 -0400 (EDT) Date: Thu, 20 Sep 2018 18:23:54 -0700 From: Andres Freund To: David Steele Cc: Michael Paquier , pgsql-committers@postgresql.org Subject: Re: pgsql: Make WAL segment size configurable at initdb time. Message-ID: <20180921012354.mvkql65radrpv4gx@alap3.anarazel.de> References: <68ea97d6-2ed9-f339-e57d-ab3a33caf3b1@pgmasters.net> <20180920235932.GD1338@paquier.xyz> <4b5568f5-72b7-5355-3450-973e11447569@pgmasters.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4b5568f5-72b7-5355-3450-973e11447569@pgmasters.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2018-09-20 21:14:51 -0400, David Steele wrote: > On 9/20/18 7:59 PM, Michael Paquier wrote: > > On Thu, Sep 20, 2018 at 11:48:08AM -0400, David Steele wrote: > >> > >> > >> > >> - Reports the number of blocks (pages) in a WAL segment file. > >> - The total size of a WAL segment file in bytes is equal to > >> - wal_segment_size multiplied by wal_block_size; > >> - by default this is 16MB. See for > >> + Reports the size of write ahead log segments. > >> + The default value is 16MB. See for > >> more information. > >> > >> > > > > The GUC wal_segment_size reports as well 16MB in v10 or older versions, > > so shouldn't the mention to wal_block_size be removed even further down? > > Oddly, the GUC reports 16GB on `show wal_segment_size` but you get 2048 > when querying pg_settings. I thought that was just the normal behavior > for older versions -- and it might be a problem to change it. 16*M*B, right? If so, that's normal - pg_settings just reports the values in the underlying unit - which is XLOG_BLCKSZ, compile-time defaulting to 8KB. 8192 * 2048 = 16MB. That's the same in various other settings. Greetings, Andres Freund