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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Joe Conway <mail(at)joeconway(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 01:18:33
Message-ID: CAKFQuwaqBF_QoQC8aoqBiY4ggvBU6fR0k6CjeTQcoLy_9V4Sng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 6, 2022 at 6:16 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
> > I am a bit torn between "\dcp" (or \dsetting / \dconfig? we don't
> > necessarily need for it to be super short) and "\sc". Certainly with
> > pattern matching the interface for the "\d" commands would fit that
> > pattern. "\sc" would make sense for a thorough introspection of what is
> > in the GUC. That said, we get that with SHOW today.
>
> > So I'm leaning towards something in the "\d" family.
>
> I agree that \d-something makes the most sense from a functionality
> standpoint. But I don't want to make the name too long, even if we
> do have tab completion to help.
>
> \dconf maybe?
>
>
I don't have a strong preference, but just tossing it out there; maybe
embrace the novelty of GUC?

\dguc

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2022-04-07 01:27:23 Re: How about a psql backslash command to show GUCs?
Previous Message Tom Lane 2022-04-07 01:16:05 Re: How about a psql backslash command to show GUCs?