From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Joe Conway <mail@joeconway.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-hackers@lists.postgresql.org, Mark Dilger <mark.dilger@enterprisedb.com>
Subject: Re: How about a psql backslash command to show GUCs?
Date: Wed, 06 Apr 2022 21:16:05 -0400
Message-ID: <3201870.1649294165@sss.pgh.pa.us> (raw)
In-Reply-To: <38891fd8-dceb-c956-ec5c-61c1a3e9486d@postgresql.org>
References: <202204061758.leffczewl4kd@alvherre.pgsql>
<ae4c3347-d1c7-394f-9a7e-425af6f89a80@joeconway.com>
<3123259.1649270440@sss.pgh.pa.us>
<38891fd8-dceb-c956-ec5c-61c1a3e9486d@postgresql.org>
"Jonathan S. Katz" <jkatz@postgresql.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, jkatz@postgresql.org, mail@joeconway.com, alvherre@alvh.no-ip.org, mark.dilger@enterprisedb.com
Subject: Re: How about a psql backslash command to show GUCs?
In-Reply-To: <3201870.1649294165@sss.pgh.pa.us>
References: <202204061758.leffczewl4kd@alvherre.pgsql> <ae4c3347-d1c7-394f-9a7e-425af6f89a80@joeconway.com> <3123259.1649270440@sss.pgh.pa.us> <38891fd8-dceb-c956-ec5c-61c1a3e9486d@postgresql.org> <3201870.1649294165@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox