summaryrefslogtreecommitdiff
path: root/zlib/README.MySQL
diff options
context:
space:
mode:
authorunknown <holyfoot/hf@mysql.com/hfmain.(none)>2007-10-05 15:40:32 +0500
committerunknown <holyfoot/hf@mysql.com/hfmain.(none)>2007-10-05 15:40:32 +0500
commit6d54b5771bf3cce3e5a5e8ca295219fdbae80c00 (patch)
tree36d6a636c837dca7a96045954b04b2d4ff2b4a98 /zlib/README.MySQL
parenta3d5f64c92fdb986432ea9a61cb529c531c1e0c3 (diff)
downloadmariadb-git-6d54b5771bf3cce3e5a5e8ca295219fdbae80c00.tar.gz
Bug #30286 spatial index cause corruption and server crash!
As the result of DOUBLE claculations can be bigger than DBL_MAX constant we use in code, we shouldn't use this constatn as a biggest possible value. Particularly the rtree_pick_key function set 'min_area= DBL_MAX' relying that any rtree_area_increase result will be less so we return valid key. Though in rtree_area_increase function we calculate the area of the rectangle, so the result can be 'inf' if the rectangle is huge enough, which is bigger than DBL_MAX. Code of the rtree_pick_key modified so we always return a valid key. myisam/rt_index.c: Bug #30286 spatial index cause corruption and server crash! always set the best_key with the first key we get, so we always return somthing valid. myisam/rt_mbr.c: Bug #30286 spatial index cause corruption and server crash! function comment extended mysql-test/r/gis-rtree.result: Bug #30286 spatial index cause corruption and server crash! test result mysql-test/t/gis-rtree.test: Bug #30286 spatial index cause corruption and server crash! test case
Diffstat (limited to 'zlib/README.MySQL')
0 files changed, 0 insertions, 0 deletions