[Commits] Rev 3558: Post-merge fixes: remove DBUG_ASSERT(min_key || max_key) in file:///data0/psergey/dev2/5.3-serg/

Sergey Petrunya psergey at askmonty.org
Thu Aug 23 09:01:20 EEST 2012


At file:///data0/psergey/dev2/5.3-serg/

------------------------------------------------------------
revno: 3558
revision-id: psergey at askmonty.org-20120823060119-uno250p5tod2su08
parent: sergii at pisem.net-20120822125335-vd6llfrl0d3l2bk0
committer: Sergey Petrunya <psergey at askmonty.org>
branch nick: 5.3-serg
timestamp: Thu 2012-08-23 10:01:19 +0400
message:
  Post-merge fixes: remove DBUG_ASSERT(min_key || max_key)
=== modified file 'storage/xtradb/handler/ha_innodb.cc'
--- a/storage/xtradb/handler/ha_innodb.cc	2012-08-22 12:53:35 +0000
+++ b/storage/xtradb/handler/ha_innodb.cc	2012-08-23 06:01:19 +0000
@@ -8196,8 +8196,10 @@
 	mem_heap_t*	heap;
 
 	DBUG_ENTER("records_in_range");
-	DBUG_ASSERT(min_key || max_key);
-
+        /*
+        The following limitation was present in MySQL 5.1 but was gone in 5.5+:
+          DBUG_ASSERT(min_key || max_key);
+        */
 	ut_a(prebuilt->trx == thd_to_trx(ha_thd()));
 
 	prebuilt->trx->op_info = (char*)"estimating records in index range";



More information about the commits mailing list