Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#672 closed defect (wontfix)

Valid WKT crashes postgis parser

Reported by: strk Owned by: pramsey
Priority: high Milestone: PostGIS 1.5.3
Component: postgis Version: master
Keywords: Cc:

Description (last modified by strk)

=# select * from st_dump('GEOMETRYCOLLECTION(geometrycollection(empty),geometrycollection(empty))'); server closed the connection unexpectedly

This probably means the server terminated abnormally before or while processing the request.

The connection to the server was lost. Attempting reset: Failed.

Change History (8)

comment:1 by strk, 13 years ago

Funny enough this input doesn't kill backend:

GEOMETRYCOLLECTION(GEOMETRYCOLLECTION EMPTY, GEOMETRYCOLLECTION EMPTY)

comment:2 by strk, 13 years ago

Milestone: PostGIS 1.5.3PostGIS 2.0.0
Summary: ST_Dump crash with collection of emptiesValid WKT crashes postgis parser

Eh.. no wonder. It's the parser crashing !

 select '
GEOMETRYCOLLECTION (
        GEOMETRYCOLLECTION (EMPTY),
        GEOMETRYCOLLECTION( EMPTY)
)
'::geometry;
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

comment:3 by pramsey, 13 years ago

Milestone: PostGIS 2.0.0PostGIS 1.5.3

Not my parser…

postgis20=# select '
postgis20'# GEOMETRYCOLLECTION (
postgis20'#         GEOMETRYCOLLECTION (EMPTY),
postgis20'#         GEOMETRYCOLLECTION( EMPTY)
postgis20'# )
postgis20'# '::geometry;
ERROR:  parse error - invalid geometry
LINE 1: select '
               ^
HINT:  "...N (
        GEOMETRYCOLLECTION (EMPTY" <-- parse error at position 55 within geometry

comment:4 by robe, 13 years ago

Milestone: PostGIS 1.5.3PostGIS 1.5.4

comment:5 by pramsey, 13 years ago

Resolution: wontfix
Status: newclosed

This is the sound of me not caring… we've lived with this one for a long time, let's leave it be, it's not actually crashing the backend and it's not a WKT formulation we see often in the wild.

comment:6 by robe, 13 years ago

I'm okay with that.

comment:7 by strk, 13 years ago

Description: modified (diff)

Fine with me too, as long as the new parser doesn't crash I'm happy.

comment:8 by robe, 13 years ago

Milestone: PostGIS 1.5.4PostGIS 1.5.3

well in that case this is a 1.5.3 no fix item :)

Note: See TracTickets for help on using tickets.