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 1lAFbh-0002z8-0I for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Feb 2021 17:18:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lAFbf-00068m-SC for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Feb 2021 17:18:19 +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 1lAFbf-00068f-ML for pgsql-bugs@lists.postgresql.org; Thu, 11 Feb 2021 17:18:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lAFbd-0005Ll-HM for pgsql-bugs@lists.postgresql.org; Thu, 11 Feb 2021 17:18:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 11BHIF8f1452088; Thu, 11 Feb 2021 12:18:15 -0500 From: Tom Lane To: boshomi@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16860: Documentation: GUC Parameters are not explained In-reply-to: <16860-3c4cef71e32b4233@postgresql.org> References: <16860-3c4cef71e32b4233@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 10 Feb 2021 22:17:40 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1452086.1613063895.1@sss.pgh.pa.us> Date: Thu, 11 Feb 2021 12:18:15 -0500 Message-ID: <1452087.1613063895@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > I am missing a explanation for the abbreviation "GUC" in: > in > https://www.postgresql.org/docs/current/sepgsql.html#SEPGSQL-PARAMETERS > and https://www.postgresql.org/docs/current/pgtrgm.html#id-1.11.7.40.7 It's defined in appendix L (Acronyms). It would not be sensible to duplicate the definition at every usage. regards, tom lane