Re: How about a psql backslash command to show GUCs?

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: How about a psql backslash command to show GUCs?
Date: 2022-06-07 14:52:38
Message-ID: 29d873fa-ce53-0eeb-ddf5-0a0d38458d16@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/7/22 10:26 AM, Robert Haas wrote:
> On Mon, Jun 6, 2022 at 5:02 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2022-06-07 14:54:07 Re: broken regress tests on fedora 36
Previous Message Andrew Dunstan 2022-06-07 14:51:35 Re: JSON_TABLE output collations