On 4/9/22 12:27 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz@postgresql.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
