Wrong answer from native 3D functions in some situations

[nicklas]

select st_astext(st_3dshortestline('linestring(2 2 2, 2 2 4)'::geometry, 'linestring(0 0 4, 4 4 2)'::geometry))

has a 3D crossing at point(2 2 3) and the answer should be

LINESTRING Z (2 2 3,2 2 3)

But instead it returns

LINESTRING Z (2 2 2,2.22222222222222 2.22222222222222 2.88888888888889)

Interestingly if input is changed to

select st_astext(st_3dshortestline('linestring(2 2 1, 2 2 4)'::geometry, 'linestring(0 0 4, 4 4 2)'::geometry))

the right answer is returned.

This probably goes back to PostGIS 2.0

[nicklas]

Fixed in trunk at r13960

[nicklas]

Fixed in 2.0 at r13961 and in 2.1 at r13962