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

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Subject: Re: How about a psql backslash command to show GUCs?
Date: 2022-04-07 12:36:28
Message-ID: 5588a650-48e2-3d3d-ad36-a1ea6787a15a@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/6/22 23:02, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
>> +1 for \dconf
>
> Here's a draft patch using \dconf. No tests or docs yet.

WFM -- using some form of \d<something> makes more sense than
\s<something>, and I can't think of anything better that \dconf.

I will say that I care about context far more often than unit or type
though, so from my point of view I would switch them around with respect
to which is only shown with verbose.

Joe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-04-07 12:40:31 Re: REINDEX blocks virtually any queries but some prepared queries.
Previous Message Andrew Dunstan 2022-04-07 12:18:05 Re: pgsql: Prefetch data referenced by the WAL, take II.