[HACKERS] psql: new help related to variables are not too readable - Mailing list pgsql-hackers

From Pavel Stehule
Subject [HACKERS] psql: new help related to variables are not too readable
Date
Msg-id CAFj8pRCaZzqjygXcgrH1oRVc6=eLRgMUGY6d7iBMmF3BfJEfng@mail.gmail.com
Whole thread Raw
Responses Re: [HACKERS] psql: new help related to variables are not tooreadable
List 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

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: [HACKERS] Tuple-routing for certain partitioned tables notworking as expected
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed