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 1ncV0x-0001TB-Qe for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Apr 2022 16:29:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ncV0w-0001RU-FM for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Apr 2022 16:29:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncV0w-0001RK-6i for pgsql-hackers@lists.postgresql.org; Thu, 07 Apr 2022 16:29:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncV0u-0003LD-6n for pgsql-hackers@lists.postgresql.org; Thu, 07 Apr 2022 16:29:41 +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 237GTXKl3370143; Thu, 7 Apr 2022 12:29:33 -0400 From: Tom Lane To: Mark Dilger cc: Andrew Dunstan , David Rowley , Joe Conway , Alvaro Herrera , PostgreSQL Developers Subject: Re: How about a psql backslash command to show GUCs? In-reply-to: References: <202204061758.leffczewl4kd@alvherre.pgsql> <3123259.1649270440@sss.pgh.pa.us> <995e06b1-0e50-396e-fce3-934d5e511e27@dunslane.net> Comments: In-reply-to Mark Dilger message dated "Thu, 07 Apr 2022 09:19:33 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3370141.1649348973.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 07 Apr 2022 12:29:33 -0400 Message-ID: <3370142.1649348973@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Mark Dilger writes: > We have too many synonyms for configuration parameters. "config", "guc"= , "parameter", and "setting" are already in use. I thought we agreed on t= he other thread that "setting" means the value, and "parameter" is the thi= ng being set. Right, so the suggestion of \dsetting seems a tad off-kilter. > It's true that "config" refers to parameters in the name of pg_catalog.s= et_config, which is a pretty strong precedent, but sadly "config" also ref= ers to configuration files, the build configuration (as in the "pg_config"= tool), text search configuration, etc. I'd also thought briefly about \dpar or \dparam, but I'm not sure that that's much of an improvement. \dconf is at least in line with the docs' terminology of "configuration parameter". (Note that bare "parameter" has other meanings too, eg function parameter.) I wouldn't fight too hard if people want to lengthen it to \dconfig for consistency with set_config(). regards, tom lane