[postgis-devel] 3.1.1 Release

Paul Ramsey pramsey at cleverelephant.ca
Thu Jan 28 09:24:28 PST 2021


Seeing no howls of outrage, I am going to spin these wheels now.

P.

On Wed, Jan 27, 2021 at 1:04 PM Paragon Corporation <lr at pcorp.us> wrote:

> +1
>
> On Wed, Jan 27, 2021 at 3:59 PM Darafei "Komяpa" Praliaskouski <
> me at komzpa.net> wrote:
>
>> +1
>>
>> On Wed, Jan 27, 2021 at 11:45 PM Paul Ramsey <pramsey at cleverelephant.ca>
>> wrote:
>>
>>> Given that we're carrying a crasher in 3.1.0, I'd like to propose
>>> release of 3.1.1 right away.
>>>
>>> +1
>>>
>>> ---------- Forwarded message ---------
>>> From: Paul Ramsey <pramsey at cleverelephant.ca>
>>> Date: Wed, Jan 27, 2021 at 12:23 PM
>>> Subject: Re: [postgis-users] Postgis 3.1.0 st_makevalid crashes the
>>> PostgreSQL Server
>>> To: PostGIS Users Discussion <postgis-users at lists.osgeo.org>
>>>
>>>
>>> My installation of master on both PostGIS and GEOS does not crash, but
>>> rolling back to PostGIS 3.1.0 and GEOS master crashes. I think we should
>>> push out a minor PostGIS release ASAP.
>>>
>>> On Tue, Jan 26, 2021 at 3:37 AM Nicolas Ribot <nicolas.ribot at gmail.com>
>>> wrote:
>>>
>>>> With geos-master (3.10.0dev-CAPI-1.15.0), the buffer query from json
>>>> polygon works and returns a valid polygon, but makevalid on empty geoms
>>>> still crashes PG
>>>>
>>>> Nicolas
>>>>
>>>> On Tue, 26 Jan 2021 at 12:01, Nicolas Ribot <nicolas.ribot at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I could also reproduce it on MacOS
>>>>> (POSTGIS="3.1.0 5e2af69" [EXTENSION] PGSQL="130"
>>>>> GEOS="3.9.0-CAPI-1.16.2" SFCGAL="1.3.9" PROJ="7.2.0" GDAL="GDAL 3.2.0,
>>>>> released 2020/10/26" LIBXML="2.9.4" LIBJSON="0.15" LIBPROTOBUF="1.3.3"
>>>>> WAGYU="0.5.0 (Internal)" TOPOLOGY RASTER)
>>>>>
>>>>> The buffer operation returns an empty polygon.
>>>>> Running these queries crashes the backend (server process (PID 93524)
>>>>> was terminated by signal 6: Abort trap: 6):
>>>>>
>>>>> select st_makeValid(st_multi('POLYGON EMPTY'::geometry));
>>>>> select st_makeValid('GEOMETRYCOLLECTION EMPTY'::geometry);
>>>>> select st_makeValid('MULTIPOLYGON EMPTY'::geometry);
>>>>>
>>>>> Nicolas
>>>>>
>>>>> On Mon, 25 Jan 2021 at 11:52, Fatih Sazan <fatihsazan01 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> my postgis verison details:
>>>>>> SELECT postgis_full_version();
>>>>>>
>>>>>> POSTGIS="3.1.0 5e2af69" [EXTENSION] PGSQL="130"
>>>>>> GEOS="3.9.0-CAPI-1.16.2" PROJ="7.2.1" LIBXML="2.9.7" LIBJSON="0.13.1"
>>>>>> LIBPROTOBUF="1.3.0" WAGYU="0.5.0 (Internal)" (core procs from "3.1.0alpha2
>>>>>> b6f415d" need upgrade) TOPOLOGY (topology procs from "3.1.0alpha2 b6f415d"
>>>>>> need upgrade)
>>>>>>
>>>>>> Bjornar Skinnes <bjornar_skinnes at trimble.com>, 25 Oca 2021 Pzt,
>>>>>> 11:40 tarihinde şunu yazdı:
>>>>>>
>>>>>>> postgis/postgis:latest image today.  So I also could reproduce this
>>>>>>> error. fyi.
>>>>>>> POSTGIS="3.1.0 5e2af69" [EXTENSION] PGSQL="130"
>>>>>>> GEOS="3.7.1-CAPI-1.11.1 27a5e771" PROJ="Rel. 5.2.0, September 15th, 2018"
>>>>>>> LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.3.1" WAGYU="0.5.0
>>>>>>> (Internal)" TOPOLOGY
>>>>>>>
>>>>>>> man. 25. jan. 2021 kl. 09:35 skrev Sandro Santilli <strk at kbt.io>:
>>>>>>>
>>>>>>>> On Mon, Jan 25, 2021 at 10:19:42AM +0300, Fatih Sazan wrote:
>>>>>>>> > When I run my code running on PostGIS version 2.5, I don't get an
>>>>>>>> error but
>>>>>>>> > when I run it on 3.1 it the server gives an error and enters the
>>>>>>>> recovery
>>>>>>>> > mode every time.
>>>>>>>>
>>>>>>>> > Operating System: CentOS Linux 8
>>>>>>>> > CPE OS Name: cpe:/o:centos:centos:8
>>>>>>>> > Kernel: Linux 4.18.0-193.28.1.el8_2.x86_64
>>>>>>>> > Architecture: x86-64
>>>>>>>> >
>>>>>>>> > postgresql-13
>>>>>>>> > extension : postgis vers. 3.1.0
>>>>>>>>
>>>>>>>> This should be fixed by upgrading GEOS.
>>>>>>>> What version of GEOS are you using ?
>>>>>>>> It should be reported by:
>>>>>>>>
>>>>>>>>   SELECT postgis_full_version();
>>>>>>>>
>>>>>>>> --strk;
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>> _______________________________________________
>>>> postgis-users mailing list
>>>> postgis-users at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/postgis-users
>>>>
>>> _______________________________________________
>>> postgis-devel mailing list
>>> postgis-devel at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>>>
>>
>>
>> --
>> Darafei "Komяpa" Praliaskouski
>> OSM BY Team - http://openstreetmap.by/
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20210128/80c222ab/attachment.html>


More information about the postgis-devel mailing list