|
|||||||||||
|
Re: bk commit into 4.1 tree (holyfoot:1.2679) BUG#30286
From: Georgi Kodinov <kgeorge(at)mysql.com>
Date: Mon Aug 20 2007 - 11:54:54 EDT
See my remarks below. The fix is generally OK with few requests for comments and more tests. On 17.08.2007, at 13:29, holyfoot@mysql.com wrote: > Below is the list of changes that have just been committed into a
I don't think a valid double value can be greater than DBL_MAX
(except +/-INF and NaN). Here we may have a NaN because of the way a
key is selected : it tries to calculate the MBR area increase caused
by adding the new polygon to the key (an operation that may overflow
a double).
I suggest that you add a (very verbose) comment to rtree_area_increase () that explains why and when it can return NaN+inf and what does this mean. Then please think about (and ideally add a test) what can happen if the first two keys on the page will trigger NaN+inf case for the same value added to them. Can there be such ? If yes, how does NaN compare to a NaN (i.e. which key to choose) ? Obviously the commit comment needs rephrasing as well. Other than that I don't see other problems with the fix.
Best Regards,
-- Georgi Kodinov, Senior Software Engineer MySQL AB, Plovdiv, Bulgaria, www.mysql.com Office: +359 32 634 397 Mobile: +359 887 700 566 Skype: georgekodinov Are you MySQL certified? www.mysql.com/certification -- MySQL Code Commits Mailing List For list archives: http://lists.mysql.com/commits To unsubscribe: http://lists.mysql.com/commits?unsub=lists@pantek.comReceived on Mon Aug 20 11:55:27 2007 This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 08:39:19 EDT |
||||||||||
|
|||||||||||