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 1g3DRb-0002Fi-7d for pgsql-committers@arkaria.postgresql.org; Fri, 21 Sep 2018 04:53:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g3DRZ-0004nb-Ne for pgsql-committers@arkaria.postgresql.org; Fri, 21 Sep 2018 04:53:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g3DRZ-0004nU-IZ for pgsql-committers@lists.postgresql.org; Fri, 21 Sep 2018 04:53:29 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g3DRU-0000oo-DR for pgsql-committers@postgresql.org; Fri, 21 Sep 2018 04:53:29 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5747821F93; Fri, 21 Sep 2018 00:53:21 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 21 Sep 2018 00:53:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; 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=PrxfvvPihTifeV/Zzf2aG+1Op3i18pB38NF7Zacbl3s=; b=HZhUwL4f I6jKAAzixVZmuP9sGVmL4zRN+H0x1js9KmoRu5TLDpabDOhjjmwZ2v2CPmRX61Sn 5kdo3+wm0G+L8FlKftQ4dYenaP4FxcXfOSOOhEV1IYS93hpzixV8wUBdTD88AnH0 Og+ZxLs8eZLVmhH3+lBoDptgSZ0mCBT9+ONtbM8hScLv04PvZq0lbwBh70p4Xzgf iUe9KICQQcHU63RYVURTDpKdW9WnSE8WNhGcly4r4wuy0dEiQArUOZbC93m+bPM6 4Hfuc3uqm7g8/1WQ4My0GYkuIY+PD6iuKgWlSBoj84/5hT/bh5RJ17+xK5jB4HbM RUCObSV7TCK4bw== 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=PrxfvvPihTifeV/Zzf2aG+1Op3i18 pB38NF7Zacbl3s=; b=MddX19vBM3ffa+r24enKcymzAtr7Hw++Mo/FPJT+Dh4pI WdCm263A3GEquvYUudjlEduTDBL92o0A7nuv1ASdk0J/nthwTpaHFC0hZtcZ4aXn CYsSkvQSfGri6Lu94Ev67NITU22+X/B7imF0VPI6+cur+/pvlCPzyZl+yfECyAjC cZXVRZYGk4i1qsGyVrDlcYy4x7cIRo53Z5TsK7ev2pjc4z250MnAaXunfay+jpgO vwj6EDhmZiGiyXGrNTVspAJXOKTcnt9kk/54uoXs/rXySQntravdUCGSwR0D8l0D zLZ0MLPWR1DlVOA2dkiZBf+U+abM6YMAHqy+tMEEQ== X-ME-Proxy: X-ME-Sender: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 487ED102D4; Fri, 21 Sep 2018 00:53:19 -0400 (EDT) Date: Fri, 21 Sep 2018 13:53:16 +0900 From: Michael Paquier To: Andres Freund Cc: David Steele , pgsql-committers@postgresql.org Subject: Re: pgsql: Make WAL segment size configurable at initdb time. Message-ID: <20180921045316.GI1338@paquier.xyz> References: <68ea97d6-2ed9-f339-e57d-ab3a33caf3b1@pgmasters.net> <20180920235932.GD1338@paquier.xyz> <4b5568f5-72b7-5355-3450-973e11447569@pgmasters.net> <20180921012354.mvkql65radrpv4gx@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="va4/JQ6j8/8uipEp" Content-Disposition: inline In-Reply-To: <20180921012354.mvkql65radrpv4gx@alap3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --va4/JQ6j8/8uipEp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 20, 2018 at 06:23:54PM -0700, Andres Freund wrote: > 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. Would it bring less confusion if we append something like "When querying pg_settings"? I can see David's point the current phrasing is confusing: we don't know if this comes from pg_settings or from SHOW. It obviously refers to the former, but one can understand that it refers to the latter. A second parameter in config.sgml where this formulation is used is segment_size. -- Michael --va4/JQ6j8/8uipEp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlukeTwACgkQnvQgOdby QH0bRxAAhdhlvlzkb5JizjdA5qohbF/VZmeJXbOfKF3eVFVlJdyVtKZuAZMx1RrH ZQEJK7rWVUnXc3enrhE/PCyNpiD7xQNplzd97nOdg36Sgwg2/h3XISs4gMpCdZei 6FTUOl/02E9PPv7XwGeSxXisT3VUz66nrzfKFco3A6uvIKs+8laSjZ6nmKGmmLfr d3Rbueu3i8j9NvuH1GXoLJJo3k94FgtcLBWO+w7j9+dYrXQIS2ixeXMKazWz/Bof oX8HyTeDNkaEWVAQVfQT8tp382ppbgXdWjTSoytg0+4DrtnJyOYv0vPnmxUDv766 4jTZ1B42HeyMAYOuipWQaPh9MnpKO1VUsCQn7cPTTCIb/wsv9TFWFWth2vDQZ1s7 hNKmkRn68nSTNEAso8/6lepB/bGxlLkuy+ah0+AbIZUnIwJW/10uZiyROFuGc1fj UN4sXLVAJSccPhTo+J6ZafKiNQBQ5fuuWRbqoRnur02M4qNSFFoBJdLDv7LV4vDd KbN48v5SPr2GybKt1M+vYPCdbTrZOw2h3jn9qMrDdT2swA6ni4JMjz55jbT+8Btp muG2uOoYy6zFV5ABazsE7N8QEAZTaQSS7K3hdoGz72MNUTyCV0uszY7lpEYeIx7B a9JDwTTXAdSZDQMFsQgn7XG1fHPPXYYerh3Iat2ByIUqBdPInTU= =oOSm -----END PGP SIGNATURE----- --va4/JQ6j8/8uipEp--