Re: Variable substitution in psql backtick expansion
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Verite" <daniel@manitou-mail.org>
Cc: "Fabien COELHO" <coelho@cri.ensmp.fr>,
"Robert Haas" <robertmhaas@gmail.com>,
"Pavel Stehule" <pavel.stehule@gmail.com>,
"Corey
Huinker" <corey.huinker@gmail.com>,
"PostgreSQL Developers" <pgsql-hackers@postgresql.org>
Date: 2017-09-04T17:35:40Z
Lists: pgsql-hackers
"Daniel Verite" <daniel@manitou-mail.org> writes: > The two-space left margin on the entire block does not add that > much to readability, IMV, so maybe we could reclaim these > two characters. Well, it's a sub-list of the entire output of helpVariables(), so I think some indentation is a good idea. > That would look like the following, for example, with a 3-space margin > for the description: > AUTOCOMMIT > If set, successful SQL commands are automatically committed But we could do something close to that, say two-space indent for the variable names and four-space for the descriptions. > To me that looks like a good trade-off: it eases the size constraints > for both the description and the name of the variable, at the cost > of consuming one more line per variable, but that's why the pager > is for. Yeah, we're already past the point where it's likely that helpVariables()'s output would fit on one screen for anybody, so maybe this is the best way. 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