| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Improving psql slash usage help message |
| Date: | 2020-07-21 20:38:45 |
| Message-ID: | e7200763-8183-eeab-c1ee-e24ecc943112@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-07-21 17:10, Tom Lane wrote:
> Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com> writes:
>> So are you suggesting to not fix this or do a more detailed review and
>> assess what other psql messages can be grouped together.
>
> I was just imagining merging the entries for the commands that are
> implemented by listTables(). If you see something else that would
> be worth doing, feel free to suggest it, but that wasn't what I was
> thinking of.
It used to be like that, but it was changed here:
9491c82f7103d62824d3132b8c7dc44609f2f56b
I'm not sure which way is better. Right now, a question like "how do I
list all indexes" is easily answered by the help output. Under the
other scheme, it's hidden behind a layer of metasyntax.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-07-21 20:55:37 | Re: Which SET TYPE don't actually require a rewrite |
| Previous Message | Daniel Gustafsson | 2020-07-21 20:36:53 | Re: OpenSSL randomness seeding |