ST_Force3D functions no longer accepts M/Z value

[marcoslot]

ST_ForceBase does not add a double argument for the 3D values, so the 2-argument signature errors:

select st_force3dm('point(3 4)', 3.4);

Binder Error:
No function matches the given name and argument types 'ST_Force3DM(STRING_LITERAL, DECIMAL(2,1))'. You might need to add explicit type casts.
        Candidate functions:
        ST_Force3DM(GEOMETRY) -> GEOMETRY


LINE 1: select st_force3dm('point(3 4)', 3.4);

[Maxxen]

I could have sworn we had a test for this... but thanks for reporting! I'll investigate.