From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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 Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: How about a psql backslash command to show GUCs? |
Date: | 2022-04-09 18:50:59 |
Message-ID: | 043bcb40-052f-5c85-63ff-d6a2b5a0b7ca@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/9/22 12:27 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> 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".
Reasonable points. I don't have any objections to this proposal.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-04-09 19:06:55 | Re: shared-memory based stats collector - v70 |
Previous Message | Greg Stark | 2022-04-09 17:14:44 | Re: Commitfest wrapup |