summaryrefslogtreecommitdiff
path: root/mysql-test/t/myisam_mrr.test
Commit message (Collapse)AuthorAgeFilesLines
* make the test result independent from sizeof(void*)Sergei Golubchik2012-02-251-0/+2
|
* 5.3 mergeSergei Golubchik2012-02-241-1/+0
|
* sort status variables alphabetically in mysqld.ccSergei Golubchik2012-01-311-5/+0
|
* Make testcase stable by adding --sorted_result for SHOW STATUS commands.Sergey Petrunya2012-01-271-0/+5
|
* Update handler status variables after the last commit.Sergey Petrunya2012-01-251-0/+1
|
* Add MRR counters: Handler_mrr_init, Handler_mrr_extra_rowid_sorts, Sergey Petrunya2012-01-231-0/+52
| | | | | Handler_mrr_extra_key_sorts.
* Fixed a cost estimation bug introduced into in the function best_access_pathIgor Babaev2011-09-301-0/+8
| | | | | | | | | of the 5.3 code line after a merge with 5.2 on 2010-10-28 in order not to allow the cost to access a joined table to be equal to 0 ever. Expanded data sets for many test cases to get the same execution plans as before.
* BUG#730133: Wrong result with jkl = 7, BKA, ICP in maria-5.3 + compound indexSergey Petrunya2011-09-131-1/+42
| | | | | | | | | - Mrr_ordered_index_reader::interrupt_read() and resume_read() should save/restore not just index lookup tuple, but entire index tuple. Key parts that are not used for index lookup can be still used in pushed index condition. Failure to save/restore will cause the index condition to be evaluated over the wrong values.
* Set the default to be mrr=off,mrr_sort_keys=off:Sergey Petrunya2011-07-081-0/+3
| | | | | | | - Set the default - Adjust the testcases so that 'new' tests are run with optimizations turned on. - Pull out relevant tests from "irrelevant" tests and run them with optimizations on. - Run range.test and innodb.test with both mrr=on and mrr=off
* MWL#121-125 DS-MRR improvements Sergey Petrunya2010-12-021-1/+1
| | | | | - Address Monty's review feedback, part 5
* BUG#670417: Diverging results in maria-5.3-mwl128-dsmrr-cpk with join ↵Sergey Petrunya2010-11-081-0/+49
| | | | | | | buffer, attempt 4 - Disable identical key handling optimization when IndexConditionPushdown is used
* BUG#625841: Assertion `!table || (!table->read_set || bitmap_is_setSergey Petrunya2010-09-151-0/+29
| | | | | | - When find_all_keys() checks which table columns are needed for table scan that is done before the sorting, it should also analyze pushed index condition. This is achieved by remembering/checking pre-index-pushed condition.
* BUG#629684: Unreachable code in multi_range_read.cc in maria-5.3-dsmrr-cpkSergey Petrunya2010-09-131-0/+16
| | | | | - More test coverage
* Fix @@optimizer_switch supportSergey Petrunya2010-07-161-2/+1
| | | | | | | | - Let "mysqld --help --verbose" list all optimizer options - Make it possible to add new @@optimizer_switch flags w/o causing .result changes all over the testsuite: = Remove "select @@optimizer_switch" from tests that do not need all switches = Move @@optimizer_switch-specific tests to t/optimizer_switch.test
* - Make testcase work for both debug and releaseSergey Petrunya2009-12-221-0/+1
| | | | | | | | | | | - Add opt_range_mrr.cc file into source repo mysql-test/r/myisam_mrr.result: Make testcase work for both debug and release mysql-test/t/myisam_mrr.test: Make testcase work for both debug and release sql/Makefile.am: - Add opt_range_mrr.cc file into source repo
* MWL#67: MRR backportSergey Petrunya2009-12-221-3/+31
| | | | | | | | | | | | - Make index condition pushdown be controlled by an @@optimizer_switch flag, not by @@engine_condition_pushdown - Make MRR buffer size be controlled by @@mrr_buffer_size, not by @@read_rnd_buffer_size - Move parts of code to separate files - Code cleanup - Add --sorted_result to some SELECTs in tests.
* Backport into MariaDB-5.2 the following:Sergey Petrunya2009-12-151-1/+0
| | | | | | | | WL#2474 "Multi Range Read: Change the default MRR implementation to implement new MRR interface" WL#2475 "Batched range read functions for MyISAM/InnoDb" "Index condition pushdown for MyISAM/InnoDB" - Adjust test results (checked) - Code cleanup.
* Backport into MariaDB-5.2 the following:Sergey Petrunya2009-12-151-0/+99
WL#2474 "Multi Range Read: Change the default MRR implementation to implement new MRR interface" WL#2475 "Batched range read functions for MyISAM/InnoDb" "Index condition pushdown for MyISAM/InnoDB" Igor's fix from sp1r-igor@olga.mysql.com-20080330055902-07614: There could be observed the following problems: 1. EXPLAIN did not mention pushdown conditions from on expressions in the 'extra' column. As a result if a query had no where conditions pushed down to a table, but had on conditions pushed to this table the 'extra' column in the EXPLAIN for the table missed 'using where'. 2. Conditions for ref access were not eliminated from on expressions though such conditions were eliminated from the where condition.
View Lorry Controller Status