Re: Variable substitution in psql backtick expansion
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>,
Pavel Stehule <pavel.stehule@gmail.com>,
Corey Huinker <corey.huinker@gmail.com>,
Daniel Verite <daniel@manitou-mail.org>,
PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2017-08-27T06:13:15Z
Lists: pgsql-hackers
>> Spending developer time to write code for the hypothetical someone running >> a psql version 11 linked to a libpq < 7.4, if it can even link, does not >> look like a very good investment... Anyway, here is required the update. > > The question is the server's version, not libpq. Ok. > Modern psql does still talk to ancient servers (I tried 11devel against > 7.2 just now, to be sure). Wow:-) > The stuff in describe.c may not work well, but basic functionality > is there and I don't want to break it. Ok. Then the updated patch should work, although I do not have a setup to test that easily. -- Fabien.
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