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:52:24 -0500 |
commit | b0f2d681bdfd6a5b3e90d092f9d924f943b4fc5f (patch) | |
tree | 8c013f775828e519547571bdcd6ebde225d87322 /src/backend/access/gist/gistproc.c | |
parent | 8f742d1cdab987ba4624ad0c6aa008ced15cd87c (diff) | |
download | postgresql-b0f2d681bdfd6a5b3e90d092f9d924f943b4fc5f.tar.gz postgresql-b0f2d681bdfd6a5b3e90d092f9d924f943b4fc5f.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/gistproc.c')
0 files changed, 0 insertions, 0 deletions