From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Variable substitution in psql backtick expansion |
Date: | 2017-04-02 10:13:19 |
Message-ID: | CAFj8pRCVFp+68Tt29sZfn9tE28c2D7u_VzTcXrqjyCVBzAzRsA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2017-04-02 9:45 GMT+02:00 Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>:
>
> Hello Pavel,
>
> For this case can be nice to have function that returns server version as
>> number some like version_num() .. 10000
>>
>
> The server side information can be queried:
>
> SELECT current_setting(‘server_version_num’)
> AS server_version_num \gset
> -- 90602
>
> However client side is not so clean:
>
> \echo :VERSION
> PostgreSQL 10devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
> 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit
>
> Probably some :VERSION_NUM would make some sense. See attached PoC patch.
> Would it make sense?
Maybe better name for you CLIENT_VERSION_NUM
Can be SERVER_VERSION_NUM taken from connection info?
Regards
Pavel
>
>
> --
> Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2017-04-02 11:13:47 | Re: Variable substitution in psql backtick expansion |
Previous Message | Pavel Stehule | 2017-04-02 10:08:56 | Re: Variable substitution in psql backtick expansion |