From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | psql --help=variables lists variables that can't be set |
Date: | 2015-12-04 03:08:31 |
Message-ID: | 566103AF.1040507@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
psql --help=variables shows variables treated specially by psql. And it
tells you
Usage:
psql --set=NAME=VALUE
or \set NAME VALUE
But some of the variables listed cannot usefully be set, only read, such as
DBNAME the currently connected database name
HOST the currently connected database server
LASTOID the value of last affected OID
These can be read in a script, but there is nothing useful you can do
with them on the command line.
Also, for variables such as HISTCONTROL, IGNOREEOF, PROMPT*, they are
more commonly set in psqlrc, not on the command line.
Should we trim this list down to variables that are actually useful to
set on the command line?
I also have some concerns about the listed environment variables. The
list of libpq PG* variables is incomplete, and if we're going to curate
the list, we surely don't need to show the "not recommended" PGPASSWORD
variable.
That list probably also needs some ifdefs, since SHELL and TMPDIR don't
work on Windows, and PSQL_HISTORY only works when readline support is built.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-12-04 04:28:19 | PostgresNode::_update_pid using undefined variables in tap tests |
Previous Message | Peter Geoghegan | 2015-12-04 02:54:40 | Re: Remaining 9.5 open items |