psql: new help related to variables are not too readable

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: psql: new help related to variables are not too readable
Date: 2017-09-08 04:09:53
Message-ID: CAFj8pRCaZzqjygXcgrH1oRVc6=eLRgMUGY6d7iBMmF3BfJEfng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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
ECHO
controls what input is written to standard output
[all, errors, none, queries]
ECHO_HIDDEN
if set, display internal queries executed by backslash commands;
if set to "noexec", just show them without execution
ENCODING
current client character set encoding
FETCH_COUNT
the number of result rows to fetch and display at a time (0 = unlimited)
HISTCONTROL
controls command history [ignorespace, ignoredups, ignoreboth]
HISTFILE
file name used to store the command history
HISTSIZE
max number of commands to store in the command history
HOST

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

ECHO
controls what input is written to standard output
[all, errors, none, queries]

ECHO_HIDDEN
if set, display internal queries executed by backslash commands;
if set to "noexec", just show them without execution

ENCODING
current client character set encoding

FETCH_COUNT
the number of result rows to fetch and display at a time (0 = unlimited)

HISTCONTROL
controls command history [ignorespace, ignoredups, ignoreboth]

HISTFILE
file name used to store the command history

HISTSIZE
max number of commands to store in the command history

Regards

Pavel

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2017-09-08 04:13:47 Re: Re: proposal - psql: possibility to specify sort for describe commands, when size is printed
Previous Message Etsuro Fujita 2017-09-08 02:42:52 Re: Tuple-routing for certain partitioned tables not working as expected