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 1nWsmX-00081U-JB for pgsql-bugs@arkaria.postgresql.org; Wed, 23 Mar 2022 04:39:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nWsmV-0005pZ-Oi for pgsql-bugs@arkaria.postgresql.org; Wed, 23 Mar 2022 04:39:35 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWsmV-0005pQ-GT for pgsql-bugs@lists.postgresql.org; Wed, 23 Mar 2022 04:39:35 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWsmT-0005wu-9T for pgsql-bugs@lists.postgresql.org; Wed, 23 Mar 2022 04:39:34 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 3AE923200F81; Wed, 23 Mar 2022 00:39:32 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 23 Mar 2022 00:39:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=arkeTzbcyt7TKAzfxfQEF8bYucWHCZh3D9KIiT Zu4YE=; b=UOuu4oajqcVlwn35FsMpqzX+wdmSYEEoIVYMfk11AmaSf9+l/YCYS2 r3db6tKj0QyiCa5DBLv4g57oeJyjctXdh1NZMz1A5sAbFK99Ulc9gMXi9qY20ahk 4ZnmO+H/6/EJXQM3jib6ovxwzSXVRIjQny7reK8SmIDjl9gPyCCHSP36mZkqnGRv 0U+yTVTwXbMeqfAEdpJMVNYnyZRGNMYy6kxiLlxxUcIcWKKG80Ye2BBis8Apt5PK QoeDU8+oo2NrHYrVVlEa3Xcf3JQMlQAzDH25tPEkzq97XJoB0HhzAKhAYU3U3CWw iy6yKROqHYumn0Ip6jm8sl8/3duksA/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=arkeTzbcyt7TKAzfx fQEF8bYucWHCZh3D9KIiTZu4YE=; b=bkxdCOfXGqh2sR/9XdHafl9QxMnNpHL53 HphFwRdCXwliEJZ3Wnf8C0r/UVeLPFV4kE1UkKP96BeiveBRz6eWbk16NMP5aN0a I5rE8ckN9clm0nKmW40llNBZcfaPR4JDZcxOeVugXT3wizLmZTYFA21bU1c+TP7T iYaWf5K4AWKvFmUJshRE86i+TMUoMrQO3KXEzDZVGtjOC1e7Y/LrTyJHuyJPBXgc 80I2ACL6JMX/rIstjRu8//LfQ2FyEEr2/X/3dbnSZlyZ/6hWCgDWhiGxkjKSNywb y/RReSaKYLm+vNQlC+kcHpaVauOYsCx+v8DuPcT/SFI1xbR8eIzrg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudegiedgjeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdlfeehmdenucfjughrpeffhf fvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhu ihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrh hnpeffudeffeelgffhkedukeekvedvudfgieetkeekudelfeevhffhffdtudffieeutden ucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdr giihii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 23 Mar 2022 00:39:29 -0400 (EDT) Date: Wed, 23 Mar 2022 13:39:27 +0900 From: Michael Paquier To: troy@frericks.us, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently" Message-ID: References: <17446-929d0567c3eb9f6e@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="quGI7r5AhNABo4+2" Content-Disposition: inline In-Reply-To: <17446-929d0567c3eb9f6e@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --quGI7r5AhNABo4+2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 22, 2022 at 09:58:28PM +0000, PG Bug reporting form wrote: > https://www.postgresql.org/docs/9.6/sql-createindex.html#SQL-CREATEINDEX-= CONCURRENTLY >=20 > Suggest changing section title "Building Indexes Concurrently" to "Buildi= ng > Indexes Using the CONCURRENTLY Parameter" to eliminate any ambiguity. FWIW, I don't see the existing section title as really ambigu here, and this wording exists with 10~ years now without anybody complaining about it. REINDEX CONCURRENTLY has been introduced in the last years, and it has influenced this description, but mot by much as the same concepts as CREATE INDEX apply for the building part. -- Michael --quGI7r5AhNABo4+2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmI6pH8ACgkQnvQgOdby QH2doA//VOyAd49aBYUplaTfUNJKaRixaRUQ/319wC8n5kKrVBlejGJJxsxC8SnL 39m8dTDldSzAVBc/whIMCWl4D2s91UWtWf07zgIxoaqNWuQVaJ4WDv+JmUVyWSWs scD3lAd64vwMaKUBJozb44CwpPgN8xXX7WbKuDsvGY2BGaDtjVXalXb4ivfY7tmo iBluvrn1J9xRiZkQKRzKXmQBt8RTyMNuMI7N3e6OG8ZlXic8JCn3myjFLqT0xWZk gBR/1j+hzkPSAlITdB0SlcK1J6pk3ymaAICgZVKIL7fCLjsmR6y2K5wDHWS/OYGE hqyJIBRatMsPQnzLFTKvJWH4ubn4QoVe/bMXa1rax0Lzi4EhlTD9f5qsXLpwPxFT Ja8nN8SUEzmMZ+7JF3PQbSKGY5CmLTZ1YbWPahPBRqPWoGk/cJ5vwuL1Dbi0vZ6x 8vwkJdshg+mGYQUPkoCl0wNYu32TIDj5/g0IeZOLWGNGwS8modBpLPSz8Ys3pOTy d6AN3UlS6WwbylUUInuW4DSQbr9E4djIKJp+cyyMN/4NxgiFNKIbU021GCx6cRqO EzERIrR+1bJRxhSjO8DNDa3xCQF+3OhxHEDB5YHPgT2e773EWx1QL/djF1P8tUVs PhGoCn96J35vRU1N4zBB5Wkdl8V5j4M1FYX+zs+dmTxPdMeJ8cY= =NbLv -----END PGP SIGNATURE----- --quGI7r5AhNABo4+2--