Re: Variable substitution in psql backtick expansion
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, Robert Haas <robertmhaas@gmail.com>, Corey Huinker <corey.huinker@gmail.com>,
Daniel Verite <daniel@manitou-mail.org>, PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2017-09-04T17:01:17Z
Lists: pgsql-hackers
2017-09-04 18:56 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>: > I wrote: > > ... Or maybe we should shorten this > > variable name so it doesn't force reformatting of all this text. > > Possible ideas include "DB_VERSION_NAME", "SERVER_VER_NAME", or > > "SERVER_VERSION_STR". (The last saves only one character, whereas > > we really need to save two if we're trying not to be wider than any > > other documented variable.) > > Just had another idea: maybe make the new variable names > > SERVER_VERSION_S > SERVER_VERSION_N > VERSION_S > VERSION_N > > "_S" could usefully be read as either "string" or "short", and probably > we should document it as meaning "short". This way avoids creating any > weird inconsistencies with the existing precedent of the VERSION variable. > -1 With respect, it doesn't look well and intuitive. SERVER_VERSION_STR looks better than this. I can live very well with SERVER_VERSION_STR and SERVER_VERSION_NUM Regards Pavel > > regards, tom lane >
Commits
-
Add psql variables showing server version and psql version.
- a6c678f018d3 10.0 landed
- 9ae9d8c1549c 11.0 landed
-
Reformat psql's --help=variables output.
- 3955c8c4eda2 11.0 landed
-
Remove reinvention of stringify macro.
- cd6baed78150 10.0 landed
-
Allow psql variable substitution to occur in backtick command strings.
- f833c847b8fa 10.0 landed