Re: Improving psql slash usage help message - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Improving psql slash usage help message
Date
Msg-id e7200763-8183-eeab-c1ee-e24ecc943112@2ndquadrant.com
Whole thread Raw
In response to Re: Improving psql slash usage help message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Improving psql slash usage help message  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
List pgsql-hackers
On 2020-07-21 17:10, Tom Lane wrote:
> Hamid Akhtar <hamid.akhtar@gmail.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



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: OpenSSL randomness seeding
Next
From: Bruce Momjian
Date:
Subject: Re: Which SET TYPE don't actually require a rewrite