Re: proposal: alternative psql commands quit and exit - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: proposal: alternative psql commands quit and exit
Date
Msg-id CAMsr+YG2QKxvXiPk_4_GLh3S9qa1Xdon-Pos_JPkOPS_UROYzw@mail.gmail.com
Whole thread Raw
In response to Re: proposal: alternative psql commands quit and exit  (Avinash Kumar <avinash.vallarapu@gmail.com>)
List pgsql-hackers
On 12 December 2017 at 23:28, Avinash Kumar <avinash.vallarapu@gmail.com> wrote:
It takes a few hours to learn PostgreSQL and 1 second to remember, how to quit from psql.
Surprised to see the depth of discussion on this.

It takes sometime for a person to explore or know about PostgreSQL and install it.
Likewise, it takes him some more time to understand that there exists a "psql" to connect to it.
He knows about psql because he searched it somewhere. Just a psql --help (anybody uses help), should help me know much more about psql.
I think many people doesn't find it difficult to quit using \q.

I think its good to talk about or help with more features that helps a production database.


It's easy to dismiss usability concerns, but new users are what keeps a community healthy. Users who go "WTF is this @#$@" and bail aren't necessarily the ones you want to lose; sometimes they're just busy or are evaluating a few things at once. Early UX matters. 

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Parallel Index Scan vs BTP_DELETED and BTP_HALF_DEAD
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" inchild table must be marked NOT NULL