[postgis-devel] [PostGIS] #210: segmentation faults in lwgeom_geos.c:pgis_union_geometry_array

[PostGIS]

#210: segmentation faults in lwgeom_geos.c:pgis_union_geometry_array
------------------------+---------------------------------------------------
  Reporter:  dfuhriman  |       Owner:  robe         
      Type:  defect     |      Status:  assigned     
  Priority:  medium     |   Milestone:  postgis 1.3.7
 Component:  postgis    |     Version:  trunk        
Resolution:             |    Keywords:               
------------------------+---------------------------------------------------
Comment (by robe):

 More update.  This does not return same result as my old install.

 I tested on my windows 1.3.6 build against 8.3.7 and this

 SELECT ST_AsText(ST_Union(the_geom))
 FROM (SELECT CASE WHEN i%4 = 0 THEN ST_SetSRID(ST_Point(i,j),4326) ELSE
 NULL END As the_geom
 FROM generate_series(1,20) As i CROSS JOIN generate_series(-30, 40) As j)
 As foo;

 Returns: As I would expect -- a MULTIPOINT

 -- On my PostgreSQL 8.4 Windows 1.4b install strangely it also returns
 that mixed SRID funky error.  But to make sure I was testing a newer
 version I did retest this on my 1.4b

 SELECT ST_Union(the_geom) FROM (VALUES (ST_GeomFromText('POINT(1 2)') ),
 (null), (null) ) As foo(the_geom)

 and it returns the geometry type 0 not defined thing
 but on your new patch (my OpenSUSE patched -  it works)

 So the fact that the below is inconsistent between 1.3 and 1.4 means sadly
 :( more work to be done here.

 SELECT ST_AsText(ST_Union(the_geom))
 FROM (SELECT CASE WHEN i%4 = 0 THEN ST_SetSRID(ST_Point(i,j),4326) ELSE
 NULL END As the_geom
 FROM generate_series(1,20) As i CROSS JOIN generate_series(-30, 40) As j)
 As foo;

 I'm sure I have made this behave irradically on a 1.3 beofre.  Perhaps it
 was a 64-bit and I don't have a non-production one to test with.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/210#comment:23>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS