An error occurred fetching the project authors.
- 28 Jul, 2006 1 commit
-
-
sergefp@mysql.com authored
- Make the range-et-al optimizer produce E(#table records after table condition is applied), - Make the join optimizer use this value, - Add "filtered" column to EXPLAIN EXTENDED to show fraction of records left after table condition is applied - Adjust test results, add comments
-
- 22 Feb, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 05 Dec, 2004 1 commit
-
-
monty@mysql.com authored
-
- 11 Aug, 2004 1 commit
-
-
sergefp@mysql.com authored
The crash is eliminated but still it is weird/inefficent that ROR-intersection is used when performing updates in empty table.
-
- 28 May, 2004 1 commit
-
-
sergefp@mysql.com authored
* Fixed a problem with wrong query results for partially covering keys in ROR-index_merge * ROR-intersection retrieval plan choice algorithm now uses less disk IO - and properly processes clustered PK range scans * Fixed several minor range optimizer problems * Added more comments * Code cleanup
-
- 12 May, 2004 1 commit
-
-
sergefp@mysql.com authored
This is first cset for WL#1394 "Optimize index merge when all involved index ranges include only values with equal keys" The main idea is to exploit the fact that key scans for "key=const" return ordered sequences of rowids.
-