Opened 23 months ago

Last modified 21 months ago

#5240 closed defect

ST_DumpPoints and ST_DumpSegments crash with multipolygon that includes an empty polygon — at Version 1

Reported by: robe Owned by: pramsey
Priority: blocker Milestone: PostGIS 2.5.9
Component: postgis Version: 3.2.x
Keywords: Cc:

Description (last modified by robe) 

SELECT ST_DumpPoints(foo1.the_geom)  As result
	FROM (
			SELECT ST_GeomFromText('MULTIPOLYGON (((9 9, 9 1, 1 1, 2 4, 7 7, 9 9)), EMPTY)', 4326) As the_geom ) As foo1;

This I tested on 3.2.4dev, but haven't tested others to see how far back is the issue.

Change History (1)

comment:1 by robe, 23 months ago

Description: modified (diff)
Milestone: PostGIS 3.2.4 → PostGIS 3.0.8
Summary: ST_DumpPoints crash with multipolygon that includes an empty polygon → ST_DumpPoints and ST_DumpSegments crash with multipolygon that includes an empty polygon 
SELECT ST_DumpSegments(foo1.the_geom)  As result
							FROM (
		(SELECT ST_GeomFromText('MULTIPOLYGON (((9 9, 9 1, 1 1, 2 4, 7 7, 9 9)), EMPTY)', 4326) As the_geom ) ) As foo1 LIMIT 10;

I'm going to assume these issues have been here for a while.

Note: See TracTickets for help on using tickets.