Horton

Re: Variable substitution in psql backtick expansion

Fabien COELHO <coelho@cri.ensmp.fr>

View thread View on postgr.es
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Corey Huinker <corey.huinker@gmail.com>, Pavel Stehule <pavel.stehule@gmail.com>, Daniel Verite <daniel@manitou-mail.org>, PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2017-04-03T07:43:39Z
Lists: pgsql-hackers 
Hello Tom,

> about version numbers [...] Of course, there are probably other ways to 
> do that, but my point is that you haven't made a case why we need to put 
> this in now rather than later.

Indeed, I have not. What about having the ability to test for minor 
versions?

   \if false
     -- pre 10.0
     \q
   \endif
   SELECT :VERSION_NUM < 100002 AS minor_not_ok \gset
   \if :minor_not_ok
     \echo script requires at least pg 10.2
     \q
   \endif

Otherwise it will wait for next CF. Note that the patch is pretty minor 
and straightforward, no need to spend much time on it.

-- 
Fabien.

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.