Re: How about a psql backslash command to show GUCs? - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: How about a psql backslash command to show GUCs?
Date
Msg-id 29d873fa-ce53-0eeb-ddf5-0a0d38458d16@postgresql.org
Whole thread Raw
In response to Re: How about a psql backslash command to show GUCs?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: How about a psql backslash command to show GUCs?
List pgsql-hackers
On 6/7/22 10:26 AM, Robert Haas wrote:
> On Mon, Jun 6, 2022 at 5:02 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think a reasonable case can be made for excluding "internal" GUCs
>> on the grounds that (a) they cannot be set, and therefore (b) whatever
>> value they have might as well be considered the default.
> 
> I agree.

I think some of these could be interesting if they deviate from the 
default (e.g. "in_hot_standby") as it will give the user context on the 
current state of the system.

However, something like that is still fairly easy to determine (e.g. 
`pg_catalog.pg_is_in_recovery()`). And looking through the settings 
marked "internal" showing the non-defaults may not provide much 
additional context to a user.

+1 for excluding them.

Jonathan

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: JSON_TABLE output collations
Next
From: Andrew Dunstan
Date:
Subject: Re: broken regress tests on fedora 36