Passing zero as max_length to ST_Segmentize() causes crash
|Reported by:||skwash||Owned by:||pramsey|
Running something like the following causes server process to max out the CPU and seems to require a kill -9 to stop the process (crashing postgres entirely).
SELECT ST_Segmentize(ST_MakeLine(ST_MakePoint(0,0), ST_MakePoint(1,1)), 0);
It doesn't really make sense to pass zero, but I'm sure someone else at some point will try it with worse results than what I caused myself today. A simple param validation to catch this would probably be useful to ensure idiots (like me!) don't do this on accident.
Change History (7)
comment:1 by , 12 years ago
|Milestone:||PostGIS 2.0.1 → PostGIS 1.5.4|
|Priority:||medium → blocker|
|Version:||2.0.x → 1.5.X|