Re: postgis after pg_upgrade

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Slavcho Trnkovski <strnkovski(at)gmail(dot)com>, schneider(at)ardentperf(dot)com
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: postgis after pg_upgrade
Date: 2018-12-06 15:30:18
Message-ID: d485f3f3-6c17-36b2-cbf6-d8d7db68d852@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/6/18 12:40 AM, Slavcho Trnkovski wrote:
> Hi,
> But my understanding is that this approach is used when upgrading PostGIS.

Which maybe necessary when upgrading the database:

http://postgis.net/docs/manual-2.4/postgis_installation.html#upgrading

Which seems to be what is happening in your case, as before you
reinstalled the extension you got(from OP):

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)

> 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;
>   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(at)ardentperf(dot)com <mailto:schneider(at)ardentperf(dot)com>> 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
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Phil Endecott 2018-12-06 15:43:12 Re: Limitting full join to one match
Previous Message Stephen Frost 2018-12-06 15:23:11 Re: order of reading the conf files