[postgis-users] Upgrading for postgtis 2.4.1 to 2.4.6

[Ahsan Hadi]

On Mon, Jan 14, 2019 at 5:48 PM Raúl Marín Rodríguez <rmrodriguez at carto.com>
wrote:

> > I don't think we have faced this issue with upgrade in the past...
>
> Before PG11, Postgis didn't need to check the Postgresql release at runtime
> in the SQL code. As a reference, in the function `_postgis_pgsql_version`
> we are doing the same pattern matching (`PostgreSQL ([0-9\.]+)`).
>
> I think we should be able to change it and use `server_version_num`
> instead:
> {{{
> SELECT current_setting('server_version_num');
> }}}
>
> Can you confirm that in your case that shows 10613 or something like that?
>

 SELECT current_setting('server_version_num');
current_setting
-----------------
100006
(1 row)


> If that's the case, I'll open a ticket to address it and backport it.
>
> --
> Raúl Marín Rodríguez
> carto.com
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users



-- 
Ahsan Hadi
Snr Director Product Development
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +92-51-8358874
Mobile: +92-333-5162114

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20190114/53b4ee3d/attachment.html>