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 1neJt1-0007zB-DD for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Apr 2022 17:01:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1neJsz-0001MK-Dk for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Apr 2022 17:01:01 +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 1neJsz-0001MB-2V for pgsql-hackers@lists.postgresql.org; Tue, 12 Apr 2022 17:01:01 +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 1neJss-00076I-47; Tue, 12 Apr 2022 17:00:59 +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 23CH0fts816941; Tue, 12 Apr 2022 13:00:42 -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> <4115803.1649521632@sss.pgh.pa.us> <043bcb40-052f-5c85-63ff-d6a2b5a0b7ca@postgresql.org> <495595.1649704355@sss.pgh.pa.us> <9439380b-a81f-c910-f527-db4d470b026b@postgresql.org> <531275.1649707882@sss.pgh.pa.us> <7bba5a32-65fe-04e1-7c36-efd963a625c9@postgresql.org> <807242.1649776780@sss.pgh.pa.us> Comments: In-reply-to "Jonathan S. Katz" message dated "Tue, 12 Apr 2022 12:36:55 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <816939.1649782841.1@sss.pgh.pa.us> Date: Tue, 12 Apr 2022 13:00:41 -0400 Message-ID: <816940.1649782841@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Jonathan S. Katz" writes: > On 4/12/22 11:19 AM, Tom Lane wrote: >> It'd just look like this, I think. I see from looking at guc.c that >> boot_val can be NULL, so we'd better use IS DISTINCT FROM. > I tested it and I like this a lot better, at least it's much more > consolidated. They all seem to be generated (directories, timezones, > collations/encodings). Yeah, most of what shows up in a minimally-configured installation is postmaster-computed settings like config_file, rather than things that were actually set by the DBA. Personally I'd rather hide the ones that have source = 'override', but that didn't seem to be the consensus. > The one exception to this seems to be "max_stack_depth", which is > rendering on my "\dconfig" though I didn't change it, an it's showing > it's default value of 2MB. "boot_val" says 100, "reset_val" says 2048, > and it's commented out in my postgresql.conf. Do we want to align that? I don't think there's any principled thing we could do about that in psql. The boot_val is a conservatively small 100kB, but we crank that up automatically based on getrlimit(RLIMIT_STACK), so on any reasonable platform it's going to show as not being default. regards, tom lane