Re: Variable substitution in psql backtick expansion - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Variable substitution in psql backtick expansion
Date
Msg-id alpine.DEB.2.20.1704021805550.4632@lancre
Whole thread Raw
In response to Re: Variable substitution in psql backtick expansion  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: Variable substitution in psql backtick expansion
List pgsql-hackers
Hello Corey,

> I'm anxious to help with these patches, but they seem a bit of a moving
> target. Happy to jump in and review as soon as we've settled on what should
> be done.

The "v3" I sent basically adds both client & server version numbers in 
client-side variables, basically same code as suggested by Pavel for the 
server version, and some documentation.

The questions are:
 - which version should be provided (10.0 100000 ...)
 - how should they be named?
   In v3 there is VERSION{,_NAME,_NUM} for client and   SERVER_VERSION_{NUM,NAME} or SVERSION_NUM suggested   by Pavel
forserver.
 
 - how desirable/useful is it to have this in 10?
   Despite that this was not submitted in the relevant CF...   I created an entry in the July one, but this is for 11.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Undefined psql variables
Next
From: "Daniel Verite"
Date:
Subject: Re: Suggested fix for \p and \r in psql