Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnaeG-0002SP-MT for pgsql-bugs@arkaria.postgresql.org; Wed, 17 Jul 2019 03:30:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hnaeF-0003fE-Ie for pgsql-bugs@arkaria.postgresql.org; Wed, 17 Jul 2019 03:30:31 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnaeF-0003f6-BF for pgsql-bugs@lists.postgresql.org; Wed, 17 Jul 2019 03:30:31 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnaeD-0003y4-CN for pgsql-bugs@lists.postgresql.org; Wed, 17 Jul 2019 03:30:30 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0D03122470; Tue, 16 Jul 2019 23:30:28 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 16 Jul 2019 23:30:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=sC/6OI1LUFgkR5LwKNOseQKiosv yBlho1dAh7KTulgc=; b=vWNDoEmdOHBunF+D7fbId/7bIpo9NKs4rtBc+4+KI+f j59amlANLqEz+1Ri8iGFxeZt8iKx9Q0sR7Mx5avzMm3/bhTmMZDssXpG7/hV95hw i4U3jQd2UFzc6fCbl9H5emMs4c1LBwWJafPi7l6+/xOGdsbF7j2dfvBZW7Ej5Nc9 eBxpbarRLwLhxxGKmdjGvH1l87EoZdg+uDuVsaIQvtdRURqef+KYd3D5NMQgMfgK SdikIst++Tu+2ZNF5XUdLdwD7eXiUXvpW8w9Oip/HU1kmbbtGYnzNAz5rbhxgziW Yr8gAxNRn5d8sFHdSJ/tBz0SKGAc4RQBHiWYiOq3f3Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm3; bh=sC/6OI 1LUFgkR5LwKNOseQKiosvyBlho1dAh7KTulgc=; b=g03q7MSLJWNqvRy+Y0T7bq uX8UqWlYHrizhaKhm6TGNSuLWVFxNE9mrMoRAIYAMq2KwldElODF3nRggzxCg/Rz 5ursXHl2eL2D66RT8AdzNxCaDxq5jpxkgOhPxvkvI5J3hbm1Q4aN5tKNq1Lf2ebO 3hY3OPL4W+lxpH+LU9Oysm5bUrTku0GTHBoZQGQHvIsaQYieFHMgvfQubpaEenca FbWJnXdbXpr9cpURZDAlzQm1Q2EPETri25n3E0f/FYL1vPcq4dApZAvsZnEz0lqR s4H47B8tkBOVdinBPOUlpD3l8J/Jt3xgTPAhGjMdOSFHKbKW9z3RzklLFbAMOvDA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddriedugdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdejtddmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecukfhppeduudekrddvge durddvgeelrddvtddvnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehp rghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgepud X-ME-Proxy: Received: from paquier.xyz (mp76f1f9ca.ap.nuro.jp [118.241.249.202]) by mail.messagingengine.com (Postfix) with ESMTPA id 7DF7480059; Tue, 16 Jul 2019 23:30:26 -0400 (EDT) Date: Wed, 17 Jul 2019 12:30:23 +0900 From: Michael Paquier To: basil.bourque@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15909: Doc for `initdb` on `--data-checksums` says "cannot be changed later", but *can* be in Pg 12. Message-ID: <20190717033023.GG2130@paquier.xyz> References: <15909-e9d74271f1647472@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KscVNZbUup0vZz0f" Content-Disposition: inline In-Reply-To: <15909-e9d74271f1647472@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --KscVNZbUup0vZz0f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 16, 2019 at 04:10:52PM +0000, PG Bug reporting form wrote: > But now in Postgres 12, the `pg_checksums` command can enable or disable > checksums on an existing cluster. My fault here. As it is an initdb option, it is pretty obvious that it is an initialization-time option. My take is to simply remove the sentence completely instead of adding an extra reference to pg_checksums. Thoughts? -- Michael --KscVNZbUup0vZz0f Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl0ulk8ACgkQnvQgOdby QH1NHg/+KeC8YbD+w1itswMwgsBLokapN2WQ+2GU6ZOV2uURq758fqqUNIKeiNRo 9pBvwpWRlTryQr3sfTVRA64U2jvDyqOu8N3c6ovJhinERFyz6y0y/X77qDRVl5QW TFZqMDXKuHDe1U75F8Q8bAygVj6/NG8JI3QXBDqaYtjXylp+GfFBx6pIVBZQfm8p GzdC1sqYKlgfIXF6RQlyTfoymZ4FlhCqkvVEX/U8O0umXFqNoUTvy2pWzvV5hQEU iJxQ5zqZJzc6UWoRRhC858ReDIx6oHa8lXvbjV41dI7doJfQpCGDDPcCGNnuFW/d HXTweZWinF9RR4Ujgs9mNCO09xVX+rQxl5OhAu0N5mVjXQ610HH+DMfEt2aQi+2V V5ZeaA6D1QLcAFqOAF08Du85ANqmxG2J8tQDfE6sKAxUEiCwyHDx4006j5yCoYZM Am4T3YDKp3vq46T1k6qpvQ5auF7N75hlBEb0q+v1hQlkTCoPT6VoW2n++cWqme6U 2P7gz1krTnSfQ4E8kTUfRa8R4HeWz3HE4RGQju+BlOGaxR/F4PtldbXlfnsee6PO S5ey0KLIPe9XYCIpUDZhp0cM/1wH25igvPGD/bFdOBPDzPV2Y/+vjnyBA5phzMTF icpGBNod4iUYOOtWkDhbeiv2tkI805eYtozXclDazghpKIntilQ= =h4d7 -----END PGP SIGNATURE----- --KscVNZbUup0vZz0f--