Re: Variable substitution in psql backtick expansion

Daniel Verite <daniel@manitou-mail.org>

From: "Daniel Verite" <daniel@manitou-mail.org>

To: "Fabien COELHO" <coelho@cri.ensmp.fr>

Cc: "Corey Huinker" <corey.huinker@gmail.com>,"Pavel Stehule" <pavel.stehule@gmail.com>,"Greg Stark" <stark@mit.edu>,"Tom Lane" <tgl@sss.pgh.pa.us>,"PostgreSQL Developers" <pgsql-hackers@postgresql.org>

Date: 2017-04-14T16:37:09Z

Lists: pgsql-hackers

	Fabien COELHO wrote:

> Pavel also suggested some support for TEXT, although I would like to see a 
> use case. That could be another extension to the engine.

SQLSTATE is text.

Also when issuing "psql -v someoption=value -f script", it's reasonable
to want to compare :someoptionvar to 'somevalue' in the script.

Best regards,
-- 
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

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