[postgis-tickets] [PostGIS] #5122: Crash on aurora postgres topology add_polygon

[PostGIS]

#5122: Crash on aurora postgres topology add_polygon
-----------------------+---------------------------
  Reporter:  robe      |      Owner:  robe
      Type:  defect    |     Status:  assigned
  Priority:  medium    |  Milestone:  PostGIS 3.1.6
 Component:  topology  |    Version:  3.1.x
Resolution:            |   Keywords:
-----------------------+---------------------------
Description changed by robe:

Old description:

> The performance suite is failing on aurora postgres in a couple of cases.
>
> In the topology case it crashes
>
> https://git.osgeo.org/gitea/postgis/postgis-performance
>

> {{{
> POSTGIS="3.1.5 0" [EXTENSION] PGSQL="130" GEOS="3.9.1dev-CAPI-1.14.1"
> PROJ="6.2.1" LIBXML="2.9.9" LIBJSON="0.12.99" LIBPROTOBUF="1.3.0"
> WAGYU="0.5.0 (Internal)"
> }}}
>

>
> {{{
> [02:59:23] pgtap/topology/add_polygon.sql .......
> 1..3
> 16
> psql:pgtap/topology/add_polygon.sql:13: server closed the connection
> unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> psql:pgtap/topology/add_polygon.sql:13: fatal: connection to server was
> lost
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 3/3 subtests
> }}}
>
> The add_linestring was okay except for exceeding time limits
>
> data
>
> {{{
> CREATE EXTENSION postgis_tiger_geocoder CASCADE;
> }}}
> Load data with psql from Where state boundaries are the ones in -
> http://postgis.net/extra/test-data/tiger_national.sql.bz2
>
> Test
>
> {{{
> SELECT topology.CreateTopology('topoperf', 4269) ;
> CREATE TABLE topoperf.polygon
> AS SELECT (ST_Dump(geom)).geom AS g FROM (SELECT the_geom AS geom FROM
> tiger.state) AS f;
>
> SELECT topology.TopoGeo_addPolygon('topoperf', g)
>   FROM topoperf.polygon;
>
> }}}
>
> I tested on RDS running and that passed fine including the timing
>

> {{{
> POSTGIS="3.1.4 ded6c34" [EXTENSION] PGSQL="140" GEOS="3.9.1-CAPI-1.14.2"
> PROJ="8.0.1" LIBXML="2.9.1" LIBJSON="0.15" LIBPROTOBUF="1.3.2"
> WAGYU="0.5.0 (Internal)" TOPOLOGY
> }}}
>

> I'm going to isolate further and check other systems.

New description:

 The performance suite is failing on aurora postgres in a couple of cases.

 In the topology case it crashes

 https://git.osgeo.org/gitea/postgis/postgis-performance


 {{{
 POSTGIS="3.1.5 0" [EXTENSION] PGSQL="130" GEOS="3.9.1dev-CAPI-1.14.1"
 PROJ="6.2.1" LIBXML="2.9.9" LIBJSON="0.12.99" LIBPROTOBUF="1.3.0"
 WAGYU="0.5.0 (Internal)"
 }}}



 {{{
 [02:59:23] pgtap/topology/add_polygon.sql .......
 1..3
 16
 psql:pgtap/topology/add_polygon.sql:13: server closed the connection
 unexpectedly
         This probably means the server terminated abnormally
         before or while processing the request.
 psql:pgtap/topology/add_polygon.sql:13: fatal: connection to server was
 lost
 Dubious, test returned 2 (wstat 512, 0x200)
 Failed 3/3 subtests
 }}}

 The add_linestring was okay except for exceeding time limits

 data

 {{{
 CREATE EXTENSION postgis_tiger_geocoder CASCADE;
 CREATE EXTENSION topology;
 }}}
 Load data with psql from Where state boundaries are the ones in -
 http://postgis.net/extra/test-data/tiger_national.sql.bz2

 Test

 {{{
 SELECT topology.CreateTopology('topoperf', 4269) ;
 CREATE TABLE topoperf.polygon
 AS SELECT (ST_Dump(geom)).geom AS g FROM (SELECT the_geom AS geom FROM
 tiger.state) AS f;

 SELECT topology.TopoGeo_addPolygon('topoperf', g)
   FROM topoperf.polygon;

 }}}

 I tested on RDS running and that passed fine including the timing


 {{{
 POSTGIS="3.1.4 ded6c34" [EXTENSION] PGSQL="140" GEOS="3.9.1-CAPI-1.14.2"
 PROJ="8.0.1" LIBXML="2.9.1" LIBJSON="0.15" LIBPROTOBUF="1.3.2"
 WAGYU="0.5.0 (Internal)" TOPOLOGY
 }}}


 I'm going to isolate further and check other systems.

--

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5122#comment:3>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.