Horton

Re: Variable substitution in psql backtick expansion

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
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-05T14:54:51Z
Lists: pgsql-hackers 
I wrote:
> "Daniel Verite" <daniel@manitou-mail.org> writes:
>> 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.

Done like that.  I forgot to credit you with the idea in the commit log;
sorry about that.

			regards, tom lane

Commits

  1. Add psql variables showing server version and psql version.

  2. Reformat psql's --help=variables output.

  3. Remove reinvention of stringify macro.

  4. Allow psql variable substitution to occur in backtick command strings.