<div dir="ltr">Thank you. That does indeed fix the issue.<div>After looking at this for a couple of days I actually figured it out shortly after posting to the group (-;</div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Much appreciated.</div><div>Kind regards</div><div>THOR</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 14, 2019 at 12:00 PM <<a href="mailto:postgis-users-request@lists.osgeo.org">postgis-users-request@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send postgis-users mailing list submissions to<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:postgis-users-request@lists.osgeo.org" target="_blank">postgis-users-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:postgis-users-owner@lists.osgeo.org" target="_blank">postgis-users-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of postgis-users digest..."<br>
Today's Topics:<br>
<br>
1. postgis upgrade issue (PGSQL="94" (procs need upgrade for use<br>
with "96")) (Thor Bach)<br>
2. Re: postgis upgrade issue (PGSQL="94" (procs need upgrade for<br>
use with "96")) (Darafei Komяpa Praliaskouski)<br>
<br><br><br>---------- Forwarded message ----------<br>From: Thor Bach <<a href="mailto:thor.bach@streetlightdata.com" target="_blank">thor.bach@streetlightdata.com</a>><br>To: <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>Cc: <br>Bcc: <br>Date: Thu, 14 Nov 2019 05:57:32 -0800<br>Subject: [postgis-users] postgis upgrade issue (PGSQL="94" (procs need upgrade for use with "96"))<br><div dir="ltr">I am trying to upgrade a large postgres 9.6.6 database (10TB+) from postgis 2.4.1 to 2.5.3.<div>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</div><div>When I run the '<font face="monospace">ALTER EXTENSION postgis UPDATE TO "2.5.3";</font>' command, I am getting the following error:</div><div><br></div><div><font face="monospace">ERROR: operator does not exist: gidx public.&& geography<br>LINE 1: SELECT $2 OPERATOR(public.&&) $1;<br> ^<br>HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.<br>QUERY: SELECT $2 OPERATOR(public.&&) $1;</font></div><div><br></div><div>and when I run '<font face="monospace">select postgis_full_version();</font>', I get the following output:</div><div><br></div><div><font face="monospace">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<br>" LIBJSON="0.12.1" RASTER</font></div><div><br></div><div>Obviously the '
<font face="monospace">PGSQL="94" (procs need upgrade for use with "96")
</font>
' 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 '
<font face="monospace">PGSQL="94"</font>
' message.</div><div><br></div><div>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?</div><div><br></div><div>Kind Regards</div><div><br></div><div>THOR <br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><br><br>---------- Forwarded message ----------<br>From: "Darafei \"Komяpa\" Praliaskouski" <<a href="mailto:me@komzpa.net" target="_blank">me@komzpa.net</a>><br>To: PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>Cc: <br>Bcc: <br>Date: Thu, 14 Nov 2019 17:09:45 +0300<br>Subject: Re: [postgis-users] postgis upgrade issue (PGSQL="94" (procs need upgrade for use with "96"))<br><div dir="ltr">Try the next dance:<div><br></div><div>alter extension postgis update to "2.4.1next";</div><div>alter extension postgis update to "2.4.1";<br>
alter extension postgis update to "3.0.0";<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 14, 2019 at 4:57 PM Thor Bach <<a href="mailto:thor.bach@streetlightdata.com" target="_blank">thor.bach@streetlightdata.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I am trying to upgrade a large postgres 9.6.6 database (10TB+) from postgis 2.4.1 to 2.5.3.<div>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</div><div>When I run the '<font face="monospace">ALTER EXTENSION postgis UPDATE TO "2.5.3";</font>' command, I am getting the following error:</div><div><br></div><div><font face="monospace">ERROR: operator does not exist: gidx public.&& geography<br>LINE 1: SELECT $2 OPERATOR(public.&&) $1;<br> ^<br>HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.<br>QUERY: SELECT $2 OPERATOR(public.&&) $1;</font></div><div><br></div><div>and when I run '<font face="monospace">select postgis_full_version();</font>', I get the following output:</div><div><br></div><div><font face="monospace">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<br>" LIBJSON="0.12.1" RASTER</font></div><div><br></div><div>Obviously the '
<font face="monospace">PGSQL="94" (procs need upgrade for use with "96")
</font>
' 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 '
<font face="monospace">PGSQL="94"</font>
' message.</div><div><br></div><div>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?</div><div><br></div><div>Kind Regards</div><div><br></div><div>THOR <br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div>Darafei Praliaskouski</div><div>Support me: <a href="http://patreon.com/komzpa" target="_blank">http://patreon.com/komzpa</a></div></div></div></div>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a></blockquote></div>