On 12/1/18 8:56 AM, Slavcho Trnkovski wrote:
> Hi,
>
> This will not resolve the issue I have because extension is already to
> the latest version, but it is using postgres 9.4 and it should use 9.6.
Well according to below:
POSTGIS="2.4.5 r16765"
According to this:
http://postgis.net/source/
postgis-2.4.6.tar.gz
So I am thinking it is not at the latest version.
>
> Regards,
> Slavcho
>
> On Fri, Nov 30, 2018 at 6:01 PM Paul Ramsey <pramsey@cleverelephant.ca
> <mailto:pramsey@cleverelephant.ca>> wrote:
>
> If you install the new version, and then use ‘ALTER EXTENSION
> UPDATE’ to update the SQL-side bindings, everything should improve.
>
>> On Nov 30, 2018, at 5:11 AM, Slavcho Trnkovski
>> <strnkovski@gmail.com <mailto:strnkovski@gmail.com>> wrote:
>>
>> Hi,
>>
>> I have postgresql 9.4 with postgis extension installed (latest
>> version, 2.4.5). I upgraded postgresql from 9.4 to 9.6.
>> After upgrading to 9.6 I get the following result
>> from PostGIS_full_version()
>> select PostGIS_full_version();
>>
>> postgis_full_version
>>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>> POSTGIS="2.4.5 r16765" *PGSQL="94" (procs need upgrade for use
>> with "96") *GEOS="3.6.2-CAPI-1.10.2 4d2925d6" PROJ="Rel. 4.9.3, 15
>> August 2016" GDAL="GDAL 1.11.4, released 2016/01/25"
>> LIBXML="2.9.1" LIBJSON="0.11" RASTER
>> (1 row)
>>
>> Is there any way to resolve this besides recreating the extension?
>>
>> Regards,
>> Slavcho
>
--
Adrian Klaver
adrian.klaver@aklaver.com
