aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-11-10 16:51:39 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2010-11-10 16:53:53 -0500
commit5abb72f9af64339ed97eb991b0bd3456bd651f8e (patch)
tree994463186938ccd6f614a77c29d5d65b1b4d7dfe /src/backend/access/gist
parentf0e4331d04fa007830666c5baa2c3e37cce9c3ff (diff)
downloadpostgresql-5abb72f9af64339ed97eb991b0bd3456bd651f8e.tar.gz
postgresql-5abb72f9af64339ed97eb991b0bd3456bd651f8e.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')
0 files changed, 0 insertions, 0 deletions