Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qauzM-00AgWw-L5 for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Aug 2023 09:26:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qauzL-005SUL-Ci for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Aug 2023 09:26:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qauzL-005SU2-2L for pgsql-hackers@lists.postgresql.org; Tue, 29 Aug 2023 09:26:18 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qauzI-001huT-1v for pgsql-hackers@lists.postgresql.org; Tue, 29 Aug 2023 09:26:18 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 559C62FA82B6 for ; Tue, 29 Aug 2023 11:26:15 +0200 (CEST) Received: from s980.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 45E222E2BC36; Tue, 29 Aug 2023 11:26:15 +0200 (CEST) Received: from s472.loopia.se (unknown [172.22.191.5]) by s980.loopia.se (Postfix) with ESMTP id 441EE220167B; Tue, 29 Aug 2023 11:26:15 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=disabled Received: from s981.loopia.se ([172.22.191.6]) by s472.loopia.se (s472.loopia.se [172.22.190.12]) (amavisd-new, port 10024) with UTF8LMTP id 1ok5NXRNAkq3; Tue, 29 Aug 2023 11:26:14 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s981.loopia.se (Postfix) with ESMTPSA id CAFD422B16AF; Tue, 29 Aug 2023 11:26:14 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: Standardize spelling of "power of two" From: Daniel Gustafsson In-Reply-To: <20230829.175615.682972421946735863.horikyota.ntt@gmail.com> Date: Tue, 29 Aug 2023 11:26:13 +0200 Cc: pgsql-hackers@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20230829.175615.682972421946735863.horikyota.ntt@gmail.com> To: Kyotaro Horiguchi X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 29 Aug 2023, at 10:56, Kyotaro Horiguchi = wrote: > pg_resetwal and initdb has an error message like this: >=20 > msgid "argument of --wal-segsize must be a power of 2 between 1 and = 1024" >=20 > In other parts in the tree, however, we spell it as "power of two". I > think it would make sense to standardize the spelling for > consistency. See the attached. Agreed. While we have numerous "power of 2" these were the only ones in translated user-facing messages, so I've pushed this to master (it = didn't seem worth disrupting translations for 16 as we are so close to wrapping it, = if others disagree I can backpatch). -- Daniel Gustafsson