summaryrefslogtreecommitdiff
path: root/mysql-test/main/selectivity.result
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.3 into 10.4Marko Mäkelä2019-11-121-0/+56
|\
| * merge 10.2->10.3 with conflict resolutionsAndrei Elkin2019-11-111-0/+56
| |
* | Merge 10.3 into 10.4Marko Mäkelä2019-11-061-0/+57
|\ \ | |/
| * Merge 10.2 into 10.3Marko Mäkelä2019-11-061-0/+57
| |
* | Merge 10.3 into 10.4Marko Mäkelä2019-09-231-0/+85
|\ \ | |/ | | | | Disable MDEV-20576 assertions until MDEV-20595 has been fixed.
| * Merge 10.2 into 10.3Marko Mäkelä2019-09-231-0/+85
| |
* | various test failures post-mergeSergei Golubchik2019-09-061-2/+0
| |
* | Merge branch '10.3' into 10.4Sergei Golubchik2019-09-061-3/+4
|\ \ | |/
| * Merge branch '10.2' into 10.3Monty2019-09-031-0/+6
| |
* | Merge 10.3 into 10.4, except for MDEV-20265Marko Mäkelä2019-08-231-0/+34
|\ \ | |/ | | | | | | | | | | | | The MDEV-20265 commit e746f451d57def4be679caafc29976741b3e89f7 introduces DBUG_ASSERT(right_op == r_tbl) in st_select_lex::add_cross_joined_table(), and that assertion would fail in several tests that exercise joins. That commit was skipped in this merge, and a separate fix of MDEV-20265 will be necessary in 10.4.
| * Merge 10.2 into 10.3Marko Mäkelä2019-08-211-0/+34
| |
* | Merge branch '10.3' into 10.4Oleksandr Byelkin2019-07-281-3/+3
|\ \ | |/
| * Merge branch '10.2' into 10.3Oleksandr Byelkin2019-07-261-3/+3
| |
* | MDEV-18608: Defaults for 10.4: histogram size should be setSergei Petrunia2019-02-181-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change the defaults: -histogram_size=0 +histogram_size=254 -histogram_type=SINGLE_PREC_HB +histogram_type=DOUBLE_PREC_HB Adjust the testcases: - Some have ignorable changes in EXPLAIN outputs and more counter increments due to EITS table reads. - Testcases that meaningfully depend on the old defaults are changed to use the old values.
* | MDEV-16188 Use in-memory PK filters built from range index scansIgor Babaev2019-02-031-6/+6
|/ | | | | | | | | | | | | | | | | | | | | | This patch contains a full implementation of the optimization that allows to use in-memory rowid / primary filters built for range   conditions over indexes. In many cases usage of such filters reduce   the number of disk seeks spent for fetching table rows. In this implementation the choice of what possible filter to be applied   (if any) is made purely on cost-based considerations. This implementation re-achitectured the partial implementation of the feature pushed by Galina Shalygina in the commit 8d5a11122c32f4d9eb87536886c6e893377bdd07. Besides this patch contains a better implementation of the generic   handler function handler::multi_range_read_info_const() that takes into account gaps between ranges when calculating the cost of range index scans. It also contains some corrections of the implementation of the handler function records_in_range() for MyISAM. This patch supports the feature for InnoDB and MyISAM.
* Merge branch '10.2' into 10.3Sergei Golubchik2018-09-281-4/+44
|
* Merge branch '10.2' into 10.3Sergei Golubchik2018-06-301-4/+66
|
* Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-291-0/+1535