<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Regina,</p>
<p>Thanks very much for this useful information. Yes, I appreciate
there may be breaking changes causing trouble.<br>
</p>
<p>Maybe it would be good though, to provide some basic guidance on
the PostGIS webpages regarding all of the different dependencies
that "SELECT PostGIS_Full_Version()" by default lists (GEOS, PROJ,
WAYGU), and whether or not it is possible and safe to "upgrade"
such dependencies without breaking things. <br>
</p>
<p>E.g. the reason I attempted this at all and add the 'ubuntugis'
PPA, is related to all the nice performance and functionality
enhancements I saw listed for "GEOS 3.10.1", and that Paul blogged
about quite extensively, versus the older "3.8.0" that I had
installed. Of course, you made clear that any of the newer
functionality, e.g. new functions, is not available, but the
performance enhancements should still apply, because the
underlying machinery changed. Am I right here?</p>
<p>So in any case, it probably is only useful and sensible ever to
attempt a GEOS update based on your remarks, and likely no other
updates are possible unless upgrading the whole set via a custom
re-compilation of entire PostGIS.</p>
<p>Marco <br>
</p>
<div class="moz-cite-prefix">Op 10-2-2022 om 21:15 schreef Regina
Obe:<br>
</div>
<blockquote type="cite"
cite="mid:002d01d81eba$fccbbab0$f6633010$@pcorp.us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Yes.
That version is telling you that PostGIS was compiled with
PROJ 6.3.1.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The
check is done at compile time cause we have a lot of IF DEFS
to handle various proj changes. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It’s
less of an issue with GEOS since with GEOS just means you
will not be getting the newer features. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">For
PROJ it often means misbehavior since I don’t think the
major versions are completely backward compatible with
older.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
postgis-users
[<a class="moz-txt-link-freetext" href="mailto:postgis-users-bounces@lists.osgeo.org">mailto:postgis-users-bounces@lists.osgeo.org</a>] <b>On
Behalf Of </b>Marco Boeringa<br>
<b>Sent:</b> Thursday, February 10, 2022 2:08 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [postgis-users] "value out of
range: underflow" blocking error<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi Regina,<o:p></o:p></p>
<p>This was over-optimistic. <o:p></o:p></p>
<p>I now again see the "value out of range: underflow" error.
However, this now happened after upgrade of PROJ 6.3.1 to
8.2.0. Note that last time, I also did this upgrade, as it
was a forced and automatic one suggested by the Ubuntu
"Software Updater". So in both cases after restoring my VM,
this update from PROJ 6.3.1 to 8.2.0 happened before the
issue started appearing. So it appears the issue is related
to the PROJ update, not the GEOS update as I initially
suspected.<o:p></o:p></p>
<p>One interesting thing I noted, is that the
postgis_full_version still shows 'PROJ="6.3.1"', instead of
8.2.0, despite the Synaptic Package Manager clearly showing
only 8.2.0 is installed:<o:p></o:p></p>
<pre style="background:white;padding:0.25rem;white-space:pre-wrap;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px"><span style="font-size:9.0pt;color:#333333">PostGIS version: POSTGIS="3.2.0 c3e3cc0" [EXTENSION] PGSQL="130" GEOS="3.10.1-CAPI-1.16.0" PROJ="6.3.1" LIBXML="2.9.10" LIBJSON="0.13.1" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)"<o:p></o:p></span></pre>
<pre style="background:white"><span style="font-size:9.0pt;color:#333333"><o:p> </o:p></span></pre>
<p>Now I remember a similar issue with outdated version number
for GEOS from last year when I attempted to update GEOS from
3.6.0 to 3.8.0, where Paul remarked something like that it
meant that my PostGIS "wasn't compiled with GEOS 3.8.0
support", so does this possibly also mean my current PostGIS
3.2.0 installed from the official Ubuntu repository is also
not compiled with PROJ 8.2.0 support, and I should downgrade
to 6.3.1?<o:p></o:p></p>
<p>Marco<o:p></o:p></p>
<div>
<p class="MsoNormal">Op 9-2-2022 om 12:57 schreef Marco
Boeringa:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Regina, <br>
<br>
After restoring my VM a second time, I dug a little deeper
into the problem, and I now think I understand what went
wrong: <br>
<br>
I had initially attempted to upgrade my GEOS 3.8.0 that
comes by default in the Ubuntu 20.04 install to GEOS
3.10.1 from the 'ubuntugis-unstable' PPA. <br>
<br>
To do this, after adding the PPA in Ubuntu, I checked the
'libgeos3.10.1' entry in the Synaptic Package Manager, and
clicked "Apply". This succeeded, but I did not uninstall
'libgeos3.8.0' in the same process, so I had two 'libgeos'
versions installed. <br>
<br>
This seems to have caused the issue, as after I now
uninstalled 'libgeos3.8.0', I noticed the Synaptic Package
manager updated a couple of dependent libraries to the
3.10.1 version:
'libgeos++dev','libgeos-c1v5','libgeos-dev'. So I guess
the issue with the underflow was caused by having the
outdated 3.8.0 versions of these libraries still
installed. <br>
<br>
Marco <br>
<br>
Op 8-2-2022 om 19:23 schreef Regina Obe: <br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">You have the create table statement
we can test with? <br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">-----Original Message----- <br>
From: postgis-users [<a
href="mailto:postgis-users-bounces@lists.osgeo.org"
moz-do-not-send="true">mailto:postgis-users-bounces@lists.osgeo.org</a>]
On <br>
Behalf Of Marco Boeringa <br>
Sent: Monday, February 7, 2022 2:34 PM <br>
To: <a href="mailto:postgis-users@lists.osgeo.org"
moz-do-not-send="true" class="moz-txt-link-freetext">postgis-users@lists.osgeo.org</a>
<br>
Subject: Re: [postgis-users] "value out of range:
underflow" blocking <o:p></o:p></p>
</blockquote>
<p class="MsoNormal">error <br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">One additional remark: in my case,
there is no involvement of a GiST index <o:p></o:p></p>
</blockquote>
<p class="MsoNormal">as <br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">per the PostgresPro link. It fails
in a "CREATE TABLE" type statement that <o:p></o:p></p>
</blockquote>
<p class="MsoNormal">also <br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">includes some calculations, so
there isn't any indexes yet at that stage. <br>
<br>
Op 7-2-2022 om 08:17 schreef Marco Boeringa: <br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi, <br>
<br>
Anyone else seeing this issue pop up, possibly after
a recent update <br>
to a PostgreSQL related component, or something that
PostgreSQL / <br>
PostGIS is dependent on? <br>
<br>
I am still not sure if it is caused by something in
my own coding, and <br>
I first though this might be related to an attempt
to upgrade to <br>
PostgreSQL 14, but after restoring my machine to
PostgreSQL 13(.5), I <br>
still see this error blocking the successful
execution of a crucial <br>
query in my toolchain, that used to run fine up
until recently. <br>
<br>
I noticed there has been some very recent discussion
about this same <br>
type of error on a PostgreSQL mailing list: <br>
<br>
<a
href="https://postgrespro.ru/list/thread-id/2580248"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://postgrespro.ru/list/thread-id/2580248</a>
<br>
<br>
Marco <br>
<br>
_______________________________________________ <br>
postgis-users mailing list <br>
<a href="mailto:postgis-users@lists.osgeo.org"
moz-do-not-send="true"
class="moz-txt-link-freetext">postgis-users@lists.osgeo.org</a>
<br>
<a
href="https://lists.osgeo.org/mailman/listinfo/postgis-users"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/postgis-users</a>
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal">_______________________________________________
<br>
postgis-users mailing list <br>
<a href="mailto:postgis-users@lists.osgeo.org"
moz-do-not-send="true" class="moz-txt-link-freetext">postgis-users@lists.osgeo.org</a>
<br>
<a
href="https://lists.osgeo.org/mailman/listinfo/postgis-users"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/postgis-users</a>
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal">_______________________________________________
<br>
postgis-users mailing list <br>
<a href="mailto:postgis-users@lists.osgeo.org"
moz-do-not-send="true" class="moz-txt-link-freetext">postgis-users@lists.osgeo.org</a>
<br>
<a
href="https://lists.osgeo.org/mailman/listinfo/postgis-users"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/postgis-users</a>
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal">_______________________________________________
<br>
postgis-users mailing list <br>
<a href="mailto:postgis-users@lists.osgeo.org"
moz-do-not-send="true" class="moz-txt-link-freetext">postgis-users@lists.osgeo.org</a>
<br>
<a
href="https://lists.osgeo.org/mailman/listinfo/postgis-users"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/postgis-users</a>
<o:p></o:p></p>
</blockquote>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
postgis-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/postgis-users">https://lists.osgeo.org/mailman/listinfo/postgis-users</a>
</pre>
</blockquote>
</body>
</html>