Ticket #1773 (new defect)

Opened 13 months ago

Last modified 13 months ago

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

Changed 13 months ago by strk

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.
!>

Changed 13 months ago by strk

  • summary changed from ST_UnaryUnion kills the backend when passed input with NaN values to 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.

Changed 13 months ago by strk

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

Changed 13 months ago by strk

  • summary changed from Overlay operations kill the backend when passed input with NaN values to Overlay operations kill the backend when passed input with NaN values [FIXED BY GEOS-3.3.4]

Changed 13 months ago by pramsey

  • milestone changed from PostGIS 2.0.1 to PostGIS GEOS
Note: See TracTickets for help on using tickets.