[postgis-users] "value out of range: underflow" blocking error

[Marco Boeringa]

Hi Regina,

After restoring my VM a second time, I dug a little deeper into the 
problem, and I now think I understand what went wrong:

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.

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.

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.

Marco

Op 8-2-2022 om 19:23 schreef Regina Obe:
> You have the create table statement we can test with?
>
>> -----Original Message-----
>> From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On
>> Behalf Of Marco Boeringa
>> Sent: Monday, February 7, 2022 2:34 PM
>> To: postgis-users at lists.osgeo.org
>> Subject: Re: [postgis-users] "value out of range: underflow" blocking
> error
>> One additional remark: in my case, there is no involvement of a GiST index
> as
>> per the PostgresPro link. It fails in a "CREATE TABLE" type statement that
> also
>> includes some calculations, so there isn't any indexes yet at that stage.
>>
>> Op 7-2-2022 om 08:17 schreef Marco Boeringa:
>>> Hi,
>>>
>>> Anyone else seeing this issue pop up, possibly after a recent update
>>> to a PostgreSQL related component, or something that PostgreSQL /
>>> PostGIS is dependent on?
>>>
>>> I am still not sure if it is caused by something in my own coding, and
>>> I first though this might be related to an attempt to upgrade to
>>> PostgreSQL 14, but after restoring my machine to PostgreSQL 13(.5), I
>>> still see this error blocking the successful execution of a crucial
>>> query in my toolchain, that used to run fine up until recently.
>>>
>>> I noticed there has been some very recent discussion about this same
>>> type of error on a PostgreSQL mailing list:
>>>
>>> https://postgrespro.ru/list/thread-id/2580248
>>>
>>> Marco
>>>
>>> _______________________________________________
>>> postgis-users mailing list
>>> postgis-users at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/postgis-users
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-users
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users