Hi,
But my understanding is that this approach is used when upgrading PostGIS.
I'm upgrading postgresql from 9.4 to 9.6 and PostGIS version remains the same (2.4.5).
If I execute:
drop extension postgis;
drop extension postgis;
CREATE EXTENSION postgis SCHEMA postgis;
select PostGIS_full_version();
postgis_full_version
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
POSTGIS="2.4.5 r16765" PGSQL="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
everything looks OK. Is this wrong?
Regards,
Slavcho
On Tue, Dec 4, 2018 at 7:41 PM Jeremy Schneider <schneider@xxxxxxxxxxxxxx> wrote:
On 11/30/18 05:11, Slavcho Trnkovski wrote:
> 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();
>
> ... (procs need upgrade for use with "96") ...
>
> Is there any way to resolve this besides recreating the extension?
If I'm reading the postgis docs correctly, this message specifically
means that you must do a full dump/reload of postgis-enabled databases.
http://postgis.net/docs/manual-2.4/postgis_installation.html#upgrading
> If you can't find the postgis_upgrade*.sql specific for upgrading
> your version you are using a version too early for a soft upgrade
> and need to do a HARD UPGRADE.
>
> The PostGIS_Full_Version function should inform you about the need
> to run this kind of upgrade using a "procs need upgrade" message.
>
> By HARD UPGRADE we mean full dump/reload of postgis-enabled
> databases.
--
http://about.me/jeremy_schneider
