Opened 13 years ago

Closed 10 years ago

#1773 closed defect (fixed)

Overlay operations kill the backend when passed input with NaN values [FIXED BY GEOS-3.3.4]

Reported by: strk Owned by: pramsey
Priority: critical Milestone: PostGIS GEOS
Component: postgis Version: 2.0.x
Keywords: Cc:

Description

ST_UnaryUnion doesn't survive NaN values: 

strk=# select ST_UnaryUnion( '010200000002000000000000000000F8FF000000000000F8FF0000000000000000000000000000F03F' );
The connection to the server was lost. Attempting reset: Failed.
!>

The geometry is LINESTRING(-nan -nan,0 1), created by a bogus ST_Split (#1772). Origin of this bug is #1771.

Note that this is a GEOS bug so will need to be fixed there.

Change History (6)

comment:1 by strk, 13 years ago

Non-unary union is also affected, and of course 1.5 too (being GEOS fault): 

pg15=# select ST_Union( '010200000002000000000000000000F8FF000000000000F8FF0000000000000000000000000000F03F', 'POINT EMPTY' );
The connection to the server was lost. Attempting reset: Failed.
!>

comment:2 by strk, 13 years ago

Summary: ST_UnaryUnion kills the backend when passed input with NaN values → Overlay operations kill the backend when passed input with NaN values

All overlay operations seem to suffer the same bug. Filed on GEOS trac: ​http://trac.osgeo.org/geos/ticket/530

This ticket will stay on till it's fixed there.

comment:3 by strk, 13 years ago

GEOS bug is fixed, but let's keep this open until 3.3.4 is released (before pgis 2.0.1 I would suggest..).

comment:4 by strk, 13 years ago

Summary: Overlay operations kill the backend when passed input with NaN values → Overlay operations kill the backend when passed input with NaN values [FIXED BY GEOS-3.3.4]

comment:5 by pramsey, 13 years ago

Milestone: PostGIS 2.0.1 → PostGIS GEOS

comment:6 by strk, 10 years ago

Resolution: → fixed
Status: new → closed

GEOS 3.3.9 is from September 2013... time to close this

Note: See TracTickets for help on using tickets.