Valid WKT crashes postgis parser

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

[strk]

Funny enough this input doesn't kill backend:

GEOMETRYCOLLECTION(GEOMETRYCOLLECTION EMPTY, GEOMETRYCOLLECTION EMPTY)

[strk]

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.

[pramsey]

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

[pramsey]

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.

[robe]

I'm okay with that.

[strk]

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