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 1ndDvt-0004bX-VR for pgsql-hackers@arkaria.postgresql.org; Sat, 09 Apr 2022 16:27:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ndDvs-0007au-Hi for pgsql-hackers@arkaria.postgresql.org; Sat, 09 Apr 2022 16:27:28 +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 1ndDvs-0007al-8X for pgsql-hackers@lists.postgresql.org; Sat, 09 Apr 2022 16:27:28 +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 1ndDvp-0006RF-VW; Sat, 09 Apr 2022 16:27:27 +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 239GRC7U4115804; Sat, 9 Apr 2022 12:27:13 -0400 From: Tom Lane To: "Jonathan S. Katz" cc: Julien Rouhaud , Christoph Berg , Pavel Stehule , "David G. Johnston" , Joe Conway , Mark Dilger , Andrew Dunstan , David Rowley , Alvaro Herrera , PostgreSQL Developers Subject: Re: How about a psql backslash command to show GUCs? In-reply-to: References: <3370142.1649348973@sss.pgh.pa.us> <2DB6EB50-04DF-49D1-BB5B-61C62898BB35@enterprisedb.com> <3370992.1649349445@sss.pgh.pa.us> <711e43b9-6499-6a8b-0802-fb549874658e@joeconway.com> <3400691.1649363759@sss.pgh.pa.us> <4105551.1649514677@sss.pgh.pa.us> Comments: In-reply-to "Jonathan S. Katz" message dated "Sat, 09 Apr 2022 12:14:20 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4115802.1649521632.1@sss.pgh.pa.us> Date: Sat, 09 Apr 2022 12:27:12 -0400 Message-ID: <4115803.1649521632@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Jonathan S. Katz" writes: > -1, at least for the moment. Sometimes a user doesn't know what they're > looking for coupled with being unaware of what the default value is. If > a setting is set to a default value and that value is the problematic > setting, a user should be able to see that even in a full list. Sure, but then you do "\dconfig *". With there being several hundred GUCs (and no doubt more coming), I'm not sure that "show me every GUC" is a common use-case at all, let alone so common as to deserve being the default behavior. One thing we could perhaps do to reduce confusion is to change the table heading when doing this, say from "List of configuration parameters" to "List of non-default configuration parameters". regards, tom lane