| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, 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:16:05 |
| Message-ID: | 3201870.1649294165@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-04-07 01:18:33 | Re: How about a psql backslash command to show GUCs? |
| Previous Message | Amit Langote | 2022-04-07 01:05:36 | Re: simplifying foreign key/RI checks |