[postgis-tickets] [PostGIS] #3764: PostGIS topology failures on PostgreSQL 10

PostGIS trac at osgeo.org
Mon Jun 19 12:41:42 PDT 2017 

#3764: PostGIS topology failures on PostgreSQL 10
-----------------------+---------------------------
  Reporter:  robe      |      Owner:  robe
      Type:  defect    |     Status:  reopened
  Priority:  blocker   |  Milestone:  PostGIS 2.4.0
 Component:  topology  |    Version:  trunk
Resolution:            |   Keywords:
-----------------------+---------------------------

Comment (by robe):

 Alright guess it's time to refix this.  As expected the new change to
 PostgreSQL 10 broke my fragile fix.


 {{{
 PostgreSQL 10beta1 on x86_64-pc-linux-gnu, compiled by gcc (Debian
 5.2.1-22) 5.2.1 20151010, 64-bit
   Postgis 2.4.0dev - r15433 - 2017-06-19 18:39:00
   scripts 2.4.0dev r15433
   GEOS: 3.7.0dev-CAPI-1.11.0 8fe2ce62
   PROJ: Rel. 4.9.2, 08 September 2015

 Running tests

  regress/legacy_validate .. ok
  regress/legacy_predicate .. ok
  regress/legacy_invalid .. ok
  regress/sqlmm .. ok
  regress/legacy_query .. ok
  regress/addnode .. ok
  regress/addedge .. ok
  regress/addface .. ok
  regress/addface2.5d .. ok
  regress/addtopogeometrycolumn .. ok
  regress/polygonize .. ok
  regress/st_addisoedge .. ok
  regress/st_addisonode .. ok
  regress/st_addedgemodface .. ok
  regress/st_addedgenewfaces .. ok
  regress/st_changeedgegeom .. ok
  regress/st_createtopogeo .. ok
  regress/st_getfacegeometry .. ok
  regress/st_getfaceedges .. ok
  regress/st_modedgeheal .. ok
  regress/st_modedgesplit .. ok
  regress/st_newedgeheal .. ok
  regress/st_newedgessplit .. ok
  regress/st_remedgenewface .. ok
  regress/st_remedgemodface .. ok
  regress/st_simplify .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/tmp/2_4_pg10.0w64/test_26_diff)
 -----------------------------------------------------------------------------
 --- regress/st_simplify_expected        2017-02-07 07:21:40.613359496
 +0000
 +++ /var/lib/jenkins/workspace/postgis/tmp/2_4_pg10.0w64/test_26_out
 2017-06-19 18:45:00.070826465 +0000
 @@ -1,9 +1,8 @@
  t
  L1
 -N2
 -S1|f|t
 -S2|f|t
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +N1
 +S1|f|
 +S2|f|
  L2
 -HS1|f|t
 -HS2|f|t
  f
 -----------------------------------------------------------------------------
  regress/topoelement .. ok
  regress/topoelementarray_agg .. ok
  regress/topogeo_addlinestring .. ok
  regress/topogeo_addpoint .. ok
  regress/topogeo_addpolygon .. ok
  regress/topogeom_edit .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/tmp/2_4_pg10.0w64/test_32_diff)
 -----------------------------------------------------------------------------
 --- regress/topogeom_edit_expected      2017-02-07 07:21:40.665359497
 +0000
 +++ /var/lib/jenkins/workspace/postgis/tmp/2_4_pg10.0w64/test_32_out
 2017-06-19 18:45:04.182826481 +0000
 @@ -1,8 +1,5 @@
  create|t
  simple_line_layer|1
 -1|start|1|10
 -1|add|1|30
 -1|rem|1|20
 -1|dup|1|20
 -1|mis|1|20
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
  Topology 'tt' dropped
 -----------------------------------------------------------------------------
  regress/topogeometry_type .. ok
  regress/topojson .. ok
  regress/topologysummary .. ok
  regress/topo2.5d .. ok
  regress/totopogeom .. failed (diff expected obtained:
 /var/lib/jenkins/workspace/postgis/tmp/2_4_pg10.0w64/test_37_diff)
 -----------------------------------------------------------------------------
 --- regress/totopogeom_expected 2017-02-07 07:21:40.633359496 +0000
 +++ /var/lib/jenkins/workspace/postgis/tmp/2_4_pg10.0w64/test_37_out
 2017-06-19 18:45:07.298826492 +0000
 @@ -18,13 +18,13 @@
  ERROR:  Unsupported feature type TIN
  ERROR:  Unsupported feature type TRIANGLE
  ERROR:  Unsupported feature type CIRCULARSTRING
 -POINT(0 0)|t
 -LINESTRING(0 10,10 10)|t
 -POLYGON((0 20,10 20,5 30,0 20),(2 22,8 22,5 28,2 22))|t
 -MULTIPOINT(0 -10,5 -10)|t
 -MULTILINESTRING((-1 10,-10 10),(-10 8,-2 9))|t
 -MULTIPOLYGON(((100 20,110 20,105 30,100 20),(102 22,108 22,105 28,102
 22)),((80 20,90 20,90 60,80 20)))|t
 -GEOMETRYCOLLECTION(POINT(-100 -100),LINESTRING(-100 -90,-90
 -90),POLYGON((-100 -80,-90 -80,-95 -70,-100 -80),(-98 -78,-92 -78,-95
 -72,-98 -78)),MULTIPOINT(-100 -110,-95 -110),LINESTRING
 EMPTY,MULTILINESTRING((-101 -90,-110 -90),(-110 -92,-102
 -91)),MULTIPOLYGON(((0 -80,10 -80,5 -70,0 -80),(2 -78,8 -78,5 -72,2
 -78)),((-20 -80,-10 -80,-10 -40,-20
 -80))))|GEOMETRYCOLLECTION(MULTIPOLYGON(((-100 -80,-95 -70,-90 -80,-100
 -80),(-98 -78,-92 -78,-95 -72,-98 -78)),((0 -80,5 -70,10 -80,0 -80),(2
 -78,8 -78,5 -72,2 -78)),((-20 -80,-10 -40,-10 -80,-20
 -80))),MULTILINESTRING((-110 -92,-102 -91),(-101 -90,-110 -90),(-100
 -90,-90 -90)),MULTIPOINT(-100 -110,-100 -100,-95 -110))
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
  MULTIPOINT EMPTY
  MULTIPOINT EMPTY
  MULTILINESTRING EMPTY
 @@ -32,21 +32,19 @@
  MULTIPOLYGON EMPTY
  MULTIPOLYGON EMPTY
  GEOMETRYCOLLECTION EMPTY
 -tolerance_1|0.5
 -tolerance_topo_1|0.5
 -tolerance_0|0
 -custom_search_path|0
 -#1790.1|0|0
 -#1790.2|0|0
 -#1790.3|0|0
 -#1968.1|0
 -#1968.2|0
 -tgup1.1|5|100|1
 -tgup1.2|5|200|2
 -tgup1.3|5|200|4
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
  #3359.setval|1|2|1
 -#3359.line.1|1
 -#3359.line.2|2
 -#3359.area.1|1
 -#3359.area.2|2
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
 +ERROR:  set-returning functions are not allowed in CASE at character 227
  Topology 'tt' dropped
 -----------------------------------------------------------------------------
  regress/droptopology .. ok
  regress/droptopogeometrycolumn .. ok
  regress/copytopology .. ok
  regress/createtopogeom .. ok
  regress/createtopology .. ok
  regress/gml .. ok
  regress/getnodebypoint .. ok
  regress/getedgebypoint .. ok
  regress/getfacebypoint .. ok
  regress/getringedges .. ok
  regress/gettopogeomelements .. ok
  regress/layertrigger .. ok
  regress/validatetopology .. ok
  uninstall .  /var/lib/jenkins/workspace/postgis/branches/2.4/regress/00
 -regress-install/share/contrib/postgis/uninstall_topology.sql
   /var/lib/jenkins/workspace/postgis/branches/2.4/regress/00-regress-
 install/share/contrib/postgis/uninstall_postgis.sql
 . ok (4662)

 Run tests: 51
 Failed: 3
 }}}

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3764#comment:8>
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.

More information about the postgis-tickets mailing list