From: Jonathan S. Katz <jkatz@postgresql.org>
To: Mark Dilger <mark.dilger@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: How about a psql backslash command to show GUCs?
Date: Thu, 7 Apr 2022 12:49:34 -0400
Message-ID: <5d20f64c-fbe4-243e-690a-296a3515d679@postgresql.org> (raw)
In-Reply-To: <1F53D09A-FA14-428F-AB4E-9727D0B70DC7@enterprisedb.com>
References: <202204061758.leffczewl4kd@alvherre.pgsql>
<ae4c3347-d1c7-394f-9a7e-425af6f89a80@joeconway.com>
<3123259.1649270440@sss.pgh.pa.us>
<CAApHDvoCyxBZqdvwc93cnsr_48zBY7wwYmZHhCjhgp-naiDKSA@mail.gmail.com>
<995e06b1-0e50-396e-fce3-934d5e511e27@dunslane.net>
<FF230C05-B27A-4C7B-8514-A5A21EA3D7CC@enterprisedb.com>
<3370142.1649348973@sss.pgh.pa.us>
<2DB6EB50-04DF-49D1-BB5B-61C62898BB35@enterprisedb.com>
<3370992.1649349445@sss.pgh.pa.us>
<1F53D09A-FA14-428F-AB4E-9727D0B70DC7@enterprisedb.com>
On 4/7/22 12:42 PM, Mark Dilger wrote:
>
>
>> On Apr 7, 2022, at 9:37 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> Maybe I'm atypical, but I'm probably going to use tab completion
>> either way, so it's not really more keystrokes.
>
> Same here, because after tab-completing \dcon\t\t into \dconfig, I'm likely to also tab-complete to get the list of parameters. I frequently can't recall the exact spelling of them.
This seems like the only "\d" command that would require tab completion,
given all the others are far less descriptive (\dt, \dv, etc.) And at
least from my user perspective, if I ever need anything other than \dt,
I typically have to go to \? to look it up.
I'm generally in favor of consistency, though in case skewing towards
what we expose to the user. If "\dconfig" gives a bit more across the
board, I'm OK with that. "\dparam" could be a bit confusing to end users
("parameter for what?") so I'm -1 on that.
Jonathan
Attachments:
OpenPGP_signature (application/pgp-signature, 839B) download
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: jkatz@postgresql.org, mark.dilger@enterprisedb.com, tgl@sss.pgh.pa.us, andrew@dunslane.net, dgrowleyml@gmail.com, mail@joeconway.com, alvherre@alvh.no-ip.org
Subject: Re: How about a psql backslash command to show GUCs?
In-Reply-To: <5d20f64c-fbe4-243e-690a-296a3515d679@postgresql.org>
References: <202204061758.leffczewl4kd@alvherre.pgsql> <ae4c3347-d1c7-394f-9a7e-425af6f89a80@joeconway.com> <3123259.1649270440@sss.pgh.pa.us> <CAApHDvoCyxBZqdvwc93cnsr_48zBY7wwYmZHhCjhgp-naiDKSA@mail.gmail.com> <995e06b1-0e50-396e-fce3-934d5e511e27@dunslane.net> <FF230C05-B27A-4C7B-8514-A5A21EA3D7CC@enterprisedb.com> <3370142.1649348973@sss.pgh.pa.us> <2DB6EB50-04DF-49D1-BB5B-61C62898BB35@enterprisedb.com> <3370992.1649349445@sss.pgh.pa.us> <1F53D09A-FA14-428F-AB4E-9727D0B70DC7@enterprisedb.com> <5d20f64c-fbe4-243e-690a-296a3515d679@postgresql.org>
* 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