Re: postgis after pg_upgrade - Mailing list pgsql-general

From Slavcho Trnkovski
Subject Re: postgis after pg_upgrade
Date
Msg-id CACwHmfGB36gmCKzBqACk1ZnLZXgrD0qrTtoU6NfT+=dUHruhdw@mail.gmail.com
Whole thread Raw
In response to Re: postgis after pg_upgrade  (Paul Ramsey <pramsey@cleverelephant.ca>)
Responses Re: postgis after pg_upgrade  (Rene Romero Benavides <rene.romero.b@gmail.com>)
Re: postgis after pg_upgrade  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
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.

Regards,
Slavcho

On Fri, Nov 30, 2018 at 6:01 PM Paul Ramsey <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> 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

pgsql-general by date:

Previous
From: PegoraroF10
Date:
Subject: Re: Transition Tables doesn´t have OID
Next
From: Achilleas Mantzios
Date:
Subject: Re: Transition Tables doesn´t have OID