ST_LineLocatePoint garden crasher

[robe]

This issue looks like it probably got introduced with PostGIS 2.1.7 (since that exhibits the issue and so does 2.1 and trunk), but my 2.1.5 does not (and just throws a

ERROR:  getPoint4d_p: point offset out of range
********** Error **********

error

SELECT ST_LineLocatePoint(ST_MakeLine('POINT(1 2)'::geometry, 'POINT EMPTY'::geometry), ST_Point(-11,40));

What is also interesting about this problem, is I can't make a linestring from the wkt of it:

-- gives ERROR:  geometry requires more points
SELECT 'LINESTRING(1 2)'::geometry;

But am able to using ST_MakeLine or the canonical form

SELECT ST_MakeLine('POINT(1 2)'::geometry, 'POINT EMPTY'::geometry);

SELECT '010200000001000000000000000000F03F0000000000000040'::geometry;

Which I guess is okay since we want people to be able to restore corrupt data though not necessarily create such a thing.

[robe]

okay your last commit fixed this one. Once you've backported to PostGIS 2.1, feel free to close this out.

Ready for another crasher? I'll post on another ticket.

[pramsey]

This seems gone for me in 2.1 branch now.