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 1lZAM5-0004Rr-Po for pgsql-bugs@arkaria.postgresql.org; Wed, 21 Apr 2021 10:45:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lZAM3-0003cC-8K for pgsql-bugs@arkaria.postgresql.org; Wed, 21 Apr 2021 10:45:11 +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 1lZAM3-0003c5-1y for pgsql-bugs@lists.postgresql.org; Wed, 21 Apr 2021 10:45:11 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lZALx-00087D-8Y for pgsql-bugs@lists.postgresql.org; Wed, 21 Apr 2021 10:45:10 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D4A015C0089; Wed, 21 Apr 2021 06:45:03 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 21 Apr 2021 06:45:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=58oECZ4IHrVjZ3Y7ut5Yy6D9QNv yne9vDRsiRBhgv5M=; b=dsm5rY+mMFdwovj+xROLncJaJ5W4C7k4ZQXcoWEoVeb aaR1OEjP0kj1owrrUWlwG/PnEXRc2v6yChqwvBymfxzS1oe1X7GByLBta2XpWIBc JwERuVXfdxf86i7e7rAEeGIMXabeCqA/FKnRfF6t5e+a27JlvE+DU3Im/JswPzS+ B5Qk+WUeQHB3KvzsPlpcWoD/jhBjFdPdVYivYqDOItEguBRVkTSWs40VwHRlQ3xP 3zP+3Ou/pacQdUOyeXcnGUfdw/4ONtTIV1adjAcqmlee+W0WPGezo9OQs/6aSz+a 7Q0dgWfzntpHhVopNH1O/IWcd6v1nxR5vCPbymcF+Jw== 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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=58oECZ 4IHrVjZ3Y7ut5Yy6D9QNvyne9vDRsiRBhgv5M=; b=CEhCv8XzMZDAgDDEFhfAp7 0WkJgOpCFp1kdqRBQDF/BcSN5seiKvTsfSBYRnPAjTWefetja08CX4xb0UWd7rmj sLK2k6zN7hvKJt8/1nSQJtPzdkY80BuzpyoUEv/NhZIIRdFtcB22Bq5oPP0qDB1q t4otDp6+mxn5z9ivs7cFnPcWcdbzv457UtVq9zHiPCBljGf8bMOnBgYi8iJCsz9u B/vU3PM50Tdnv5Y515I4kQ1j9CrK615Ztp/SF31WJeHjW6aj+nD1W1cXWvFJf4rl KHgIpQL1VQ0fPWkoBTm4QCOvd9SUyn5ihUo/oKs2bexxCfESG5iSyy28FGkoxmDw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddtkedgfeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdljedtmdenucfjughrpeffhf fvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhu ihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrh hnpedvgeduuefhtdeuleettdevjeehheeiveeuieegleetgeeljeelieeuieehgeevhfen ucfkphepudduuddruddtvddrudektddrudekheenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id E5B34240054; Wed, 21 Apr 2021 06:45:00 -0400 (EDT) Date: Wed, 21 Apr 2021 19:44:58 +0900 From: Michael Paquier To: Bharath Rupireddy Cc: leiyanliang@highgo.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16972: parameter parallel_leader_participation's category problem Message-ID: References: <16972-42d4b0c15aa1d5f5@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="39DypHJnJ/eOVG5l" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --39DypHJnJ/eOVG5l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 21, 2021 at 09:15:23AM +0530, Bharath Rupireddy wrote: > If we arrange only the "Asynchronous Behaviour" subsection in > alphabetical order, I think the order may not be maintained in case of > new GUCs that may get added there. Because all the other subsections > are unordered and there's no note of maintaining the order as such. > And, it looks like the relevant GUCs are grouped for better > readability. For instance, all "parallelism", "io_concurrency", "jit_" > related GUCs are together. Developers tend to add the new GUCs in > relevant areas. That's up to the committers adding them to be careful, but I of course agree that the context is important. IMV, we can do a slightly better organization in "Asynchronous Behaviour". First, backend_flush_after is independent, and could just be first. parallel_leader_participation can also be moved after max_parallel_workers without impacting the readability nor impacting the set of parallel-ish parameters grouped together. -- Michael --39DypHJnJ/eOVG5l Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmCAAioACgkQnvQgOdby QH3WdQ/+KbjaapJ5FGYT14l31HoclxyZ50txACzsWS0GpFOAihl4JskR2+5Isrrr uudni1OpuO1Y0Hdg9piPWZMeHQEh7HhU3vCjcmdObM6HvfEmc+rrFVjECYRVbZoM QG1YjkVdb8BpuL3v0owbN80qMel5Xti/UTLjx9jlD0vJZwkbjbNWOsGjW4wHpfQc onLwz7OrJAc6diUkGg/nV1yJBxuleVZoR9wqipt3sVIQDIoqScOrIUMJ2rVhOP3S safnqhoKyuJFNGj/Q10Ubkkt+wHFiEnA7+Ks/PNxp8d4+oUpFxOoJfL3jUhyBFYZ iNTtlcZtaveRP6Xe+8YKrgqXV97rCSmOIpvsnncYUN0YYW304UMvgqBttjCiRAIO W4EJVXOY1XX/Q/wgbsW8xeOXh+1h0lQUsKL3P+foO1BP/oxGWdOqbsIITvBHXKnT MRAhS9ut+kPjWpFVIZC4ZyvcY/x8X8fzrSna61+jq/IHnTOgxntR708fmKRLLYLV Hm1GFN53J7J2tMGb26Zab0+1YAru8jOum8JWlbL2oUrG+C+YbwpoutB2bLq5MHol 93+94EHp4qiDKBt7iW4Ei9i7yLjeTKAv1lQ6bPAglaymvphTDkufFHtljUMwAy24 QBycFMzbxwDa8/nUyBiU6YRYcUUV8ujewtbRo0StoDGEYQYMYJY= =XDon -----END PGP SIGNATURE----- --39DypHJnJ/eOVG5l--