[postgis-users] postgis-users Digest, Vol 213, Issue 7

[Thor Bach]

Thank you. That does indeed fix the issue.
After looking at this for a couple of days I actually figured it out
shortly after posting to the group (-;
Much appreciated.
Kind regards
THOR


On Thu, Nov 14, 2019 at 12:00 PM <postgis-users-request at lists.osgeo.org>
wrote:

> Send postgis-users mailing list submissions to
>         postgis-users at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.osgeo.org/mailman/listinfo/postgis-users
> or, via email, send a message with subject or body 'help' to
>         postgis-users-request at lists.osgeo.org
>
> You can reach the person managing the list at
>         postgis-users-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of postgis-users digest..."
> Today's Topics:
>
>    1. postgis upgrade issue (PGSQL="94" (procs need     upgrade for use
>       with "96")) (Thor Bach)
>    2. Re: postgis upgrade issue (PGSQL="94" (procs need upgrade for
>       use with "96")) (Darafei Komяpa Praliaskouski)
>
>
>
> ---------- Forwarded message ----------
> From: Thor Bach <thor.bach at streetlightdata.com>
> To: postgis-users at lists.osgeo.org
> Cc:
> Bcc:
> Date: Thu, 14 Nov 2019 05:57:32 -0800
> Subject: [postgis-users] postgis upgrade issue (PGSQL="94" (procs need
> upgrade for use with "96"))
> I am trying to upgrade a large postgres 9.6.6 database (10TB+) from
> postgis 2.4.1 to 2.5.3.
> postgresql and all extensions have been built from source.
> Several years ago the same database had been upgraded from postgresql 9.4.x
> to postgresql 9.6.6 and postgis 2.3.x to postgis 2.4.1
> When I run the 'ALTER EXTENSION postgis UPDATE TO "2.5.3";' command, I am
> getting the following error:
>
> ERROR:  operator does not exist: gidx public.&& geography
> LINE 1: SELECT $2 OPERATOR(public.&&) $1;
>                   ^
> HINT:  No operator matches the given name and argument type(s). You might
> need to add explicit type casts.
> QUERY:  SELECT $2 OPERATOR(public.&&) $1;
>
> and when I run 'select postgis_full_version();', I get the following
> output:
>
> POSTGIS="2.4.1 r16012" PGSQL="94" (procs need upgrade for use with "96")
> GEOS="3.7.2-CAPI-1.11.2 b55d2125" PROJ="Rel. 4.9.3, 15 August 2016"
> GDAL="GDAL 2.2.2, released 2017/09/15" LIBXML="2.9.4
> " LIBJSON="0.12.1" RASTER
>
> Obviously the ' PGSQL="94" (procs need upgrade for use with "96") ' part
> indicates a problem. The database has run without any issues for several
> years, but I assume the postgis upgrade fails because of the underlying
> condition that causes the ' PGSQL="94" ' message.
>
> Does  anybody know what is the fastest way to get the current postgis
> configuration into a good state so that the postgis upgrade can be
> completed without errors?
>
> Kind Regards
>
> THOR
>
>
>
>
> ---------- Forwarded message ----------
> From: "Darafei \"Komяpa\" Praliaskouski" <me at komzpa.net>
> To: PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> Cc:
> Bcc:
> Date: Thu, 14 Nov 2019 17:09:45 +0300
> Subject: Re: [postgis-users] postgis upgrade issue (PGSQL="94" (procs need
> upgrade for use with "96"))
> Try the next dance:
>
> alter extension postgis update to "2.4.1next";
> alter extension postgis update to "2.4.1";
> alter extension postgis update to "3.0.0";
>
> On Thu, Nov 14, 2019 at 4:57 PM Thor Bach <thor.bach at streetlightdata.com>
> wrote:
>
>> I am trying to upgrade a large postgres 9.6.6 database (10TB+) from
>> postgis 2.4.1 to 2.5.3.
>> postgresql and all extensions have been built from source.
>> Several years ago the same database had been upgraded from postgresql 9.4.x
>> to postgresql 9.6.6 and postgis 2.3.x to postgis 2.4.1
>> When I run the 'ALTER EXTENSION postgis UPDATE TO "2.5.3";' command, I
>> am getting the following error:
>>
>> ERROR:  operator does not exist: gidx public.&& geography
>> LINE 1: SELECT $2 OPERATOR(public.&&) $1;
>>                   ^
>> HINT:  No operator matches the given name and argument type(s). You might
>> need to add explicit type casts.
>> QUERY:  SELECT $2 OPERATOR(public.&&) $1;
>>
>> and when I run 'select postgis_full_version();', I get the following
>> output:
>>
>> POSTGIS="2.4.1 r16012" PGSQL="94" (procs need upgrade for use with "96")
>> GEOS="3.7.2-CAPI-1.11.2 b55d2125" PROJ="Rel. 4.9.3, 15 August 2016"
>> GDAL="GDAL 2.2.2, released 2017/09/15" LIBXML="2.9.4
>> " LIBJSON="0.12.1" RASTER
>>
>> Obviously the ' PGSQL="94" (procs need upgrade for use with "96") ' part
>> indicates a problem. The database has run without any issues for several
>> years, but I assume the postgis upgrade fails because of the underlying
>> condition that causes the ' PGSQL="94" ' message.
>>
>> Does  anybody know what is the fastest way to get the current postgis
>> configuration into a good state so that the postgis upgrade can be
>> completed without errors?
>>
>> Kind Regards
>>
>> THOR
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
>
>
> --
> Darafei Praliaskouski
> Support me: http://patreon.com/komzpa
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20191114/a4126939/attachment.html>