On 2017-09-08 06:09, Pavel Stehule wrote:
Hi
Now the output looks like:
AUTOCOMMIT
if set, successful SQL commands are automatically committed
COMP_KEYWORD_CASE
determines the case used to complete SQL key words
[lower, upper, preserve-lower, preserve-upper]
DBNAME
the currently connected database name
[...]
What do you think about using new line between entries in this format?
AUTOCOMMIT
if set, successful SQL commands are automatically committed
COMP_KEYWORD_CASE
determines the case used to complete SQL key words
[lower, upper, preserve-lower, preserve-upper]
DBNAME
the currently connected database name
I dislike it, it takes more screen space and leads to unneccessary
scroll-need.
The 9.6.5 formatting is/was:
AUTOCOMMIT if set, successful SQL commands are automatically
committed
COMP_KEYWORD_CASE determines the case used to complete SQL key words
[lower, upper, preserve-lower, preserve-upper]
DBNAME the currently connected database name
[...]
PGPASSWORD connection password (not recommended)
PGPASSFILE password file name
PSQL_EDITOR, EDITOR, VISUAL
editor used by the \e, \ef, and \ev commands
PSQL_EDITOR_LINENUMBER_ARG
how to specify a line number when invoking the
editor
PSQL_HISTORY alternative location for the command history file
I would prefer to revert to that more compact 9.6-formatting.
Erik Rijkers
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
