diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-11-10 16:51:39 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-11-10 16:54:44 -0500 |
commit | 1a6b4396013bc369a59df9ab3a637fe31f6d9ff5 (patch) | |
tree | 907290836c88de753e0d7963d6c39f73ece9799f /src/backend/access/gist/gistutil.c | |
parent | 2ff82b6e67f7f3910620ca0d7ca9117e375b65e4 (diff) | |
download | postgresql-1a6b4396013bc369a59df9ab3a637fe31f6d9ff5.tar.gz postgresql-1a6b4396013bc369a59df9ab3a637fe31f6d9ff5.zip |
Fix line_construct_pm() for the case of "infinite" (DBL_MAX) slope.
This code was just plain wrong: what you got was not a line through the
given point but a line almost indistinguishable from the Y-axis, although
not truly vertical. The only caller that tries to use this function with
m == DBL_MAX is dist_ps_internal for the case where the lseg is horizontal;
it would end up producing the distance from the given point to the place
where the lseg's line crosses the Y-axis. That function is used by other
operators too, so there are several operators that could compute wrong
distances from a line segment to something else. Per bug #5745 from
jindiax.
Back-patch to all supported branches.
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions