summaryrefslogtreecommitdiff
path: root/mysql-test/main/innodb_ext_key.test
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-30032: EXPLAIN FORMAT=JSON output: print costsSergei Petrunia2023-02-031-2/+4
| | | | Basic printout for join and table execution costs.
* Added test cases for preceding testMonty2023-02-031-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This includes all test changes from "Changing all cost calculation to be given in milliseconds" and forwards. Some of the things that caused changes in the result files: - As part of fixing tests, I added 'echo' to some comments to be able to easier find out where things where wrong. - MATERIALIZED has now a higher cost compared to X than before. Because of this some MATERIALIZED types have changed to DEPENDEND SUBQUERY. - Some test cases that required MATERIALIZED to repeat a bug was changed by adding more rows to force MATERIALIZED to happen. - 'Filtered' in SHOW EXPLAIN has in many case changed from 100.00 to something smaller. This is because now filtered also takes into account the smallest possible ref access and filters, even if they where not used. Another reason for 'Filtered' being smaller is that we now also take into account implicit filtering done for subqueries using FIRSTMATCH. (main.subselect_no_exists_to_in) This is caluculated in best_access_path() and stored in records_out. - Table orders has changed because more accurate costs. - 'index' and 'ALL' for small tables has changed to use 'range' or 'ref' because of optimizer_scan_setup_cost. - index can be changed to 'range' as 'range' optimizer assumes we don't have to read the blocks from disk that range optimizer has already read. This can be confusing in the case where there is no obvious where clause but instead there is a hidden 'key_column > NULL' added by the optimizer. (main.subselect_no_exists_to_in) - Scan on primary clustered key does not report 'Using Index' anymore (It's a table scan, not an index scan). - For derived tables, the number of rows is now 100 instead of 2, which can be seen in EXPLAIN. - More tests have "Using index for group by" as the cost of this optimization is now more correct (lower). - A primary key could be preferred for a normal key, even if it would access more rows, as it's faster to do 1 lokoup and 3 'index_next' on a clustered primary key than one lookup trough a secondary. (main.stat_tables_innodb) Notes: - There was a 4.7% more calls to best_extension_by_limited_search() in the main.greedy_optimizer test. However examining the test results it looked that the plans where slightly better (eq_ref where more chained together) so I assume this is ok. - I have verified a few test cases where there was notable/unexpected changes in the plan and in all cases the new optimizer plans where faster. (main.greedy_optimizer and some others)
* Merge branch 'bb-10.11-vp-MDEV-27691' into 10.11Oleksandr Byelkin2022-10-171-0/+4
|\
| * Merge branch 'bb-10.5-all-builders' into bb-10.6-all-buildersLena Startseva2022-09-271-0/+4
| |\
| | * Merge branch 'bb-10.4-all-builders' into bb-10.5-all-buildersLena Startseva2022-09-261-0/+4
| | |\
| | | * Merge branch 'bb-10.3-all-builders' into bb-10.4-all-buildersLena Startseva2022-09-231-0/+4
| | | |\
| | | | * MDEV-27691: make working view-protocolLena Startseva2022-09-231-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tests with checking metadata or that cannot be run with the view-protocol are excluded from --view-protocol. For tests that do not allow the use of an additional connection, the util connection is disabled with "--disable_service_connection". Also cases with bugs for --view-protocol are disabled.
* | | | | Merge 10.5 into 10.6Marko Mäkelä2022-10-061-0/+1
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | Merge 10.4 into 10.5Marko Mäkelä2022-10-061-0/+1
| |\ \ \ \ | | |/ / / | |/| | |
| | * | | Disable valgrind for test in main that takes > 200 secondsMonty2022-10-041-0/+1
| | |/ / | | | | | | | | | | | | One can run these with --valgrind --big
* | | | MDEV-4750 follow-up: Reduce disabling innodb_stats_persistentMarko Mäkelä2021-08-311-0/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This essentially reverts commit 4e89ec6692786bc1cbdce64d43d8e85a5d247dab and only disables InnoDB persistent statistics for tests where it is desirable. By design, InnoDB persistent statistics will not be updated except by ANALYZE TABLE or by STATS_AUTO_RECALC. The internal transactions that update persistent InnoDB statistics in background tasks (with innodb_stats_auto_recalc=ON) may cause nondeterministic query plans or interfere with some tests that deal with other InnoDB internals, such as the purge of transaction history.
* | | Merge remote-tracking branch 10.4 into 10.5Daniel Black2021-02-261-0/+1
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2021-02-251-0/+1
| |\ \ | | |/
| | * Merge 10.2 into 10.3Marko Mäkelä2021-02-251-0/+1
| | |
* | | Merge branch '10.4' into 10.5Sergei Golubchik2021-02-231-2/+21
|\ \ \ | |/ /
| * | Merge branch '10.3' into 10.4Sergei Golubchik2021-02-231-2/+21
| |\ \ | | |/
| | * Merge branch '10.2' into 10.3Sergei Golubchik2021-02-221-0/+19
| | |
* | | Merge 10.4 into 10.5Marko Mäkelä2020-10-301-2/+3
|\ \ \ | |/ /
| * | Try to stabilize main.innodb_ext_key,offMarko Mäkelä2020-10-301-2/+3
| | | | | | | | | | | | | | | Thanks to Varun Gupta for suggesting this. This seems to make main.innodb_ext_key,off more stable.
* | | Merge 10.4 into 10.5Marko Mäkelä2020-10-301-1/+3
|\ \ \ | |/ /
| * | MDEV-23991 fixup: Initialize the memoryMarko Mäkelä2020-10-301-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also, revert the work-around for the test that was attempted in commit 85613a32477ef4b8fb9aefba5f61689028f3ff87. This issue was caught by MemorySanitizer as well as on the Microsoft Windows debug builds, thanks to /MD being used starting with 10.4. The code fix will also be applied to 10.2 because the regression was introduced in commit afc9d00c66db946c8240fe1fa6b345a3a8b6fec1.
| * | After-merge fix: main,innodb_ext_key,offMarko Mäkelä2020-10-291-5/+5
| | | | | | | | | | | | | | | | | | | | | For some reason, in the test main,innodb_ext_key,off we frequently get unexpected EXPLAIN output, in particular on Microsoft Windows debug builders. Let us comment out that EXPLAIN statement for now.
| * | Merge 10.3 into 10.4Marko Mäkelä2020-10-291-1/+3
| |\ \ | | |/
* | | Merge 10.4 into 10.5Marko Mäkelä2020-09-041-221/+1
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-09-031-221/+1
| |\ \ | | |/
| | * Merge 10.2 into 10.3Marko Mäkelä2020-09-031-220/+1
| | |
* | | MDEV-22119: main.innodb_ext_key fails sporadicallyVarun Gupta2020-06-121-0/+4
| | | | | | | | | | | | Made the test stable by adding more rows so the range scan is cheaper than table scan.
* | | MDEV-18650: Options deprecated in previous versions - storage_engineVicențiu Ciorbaru2020-02-131-1/+1
|/ / | | | | | | | | | | | | Remove usage of deprecated variable storage_engine. It was deprecated in 5.5 but it never issued a deprecation warning. Make it issue a warning in 10.5.1. Replaced with default_storage_engine.
* | Merge branch '10.3' into 10.4Sergei Golubchik2019-09-061-0/+3
|\ \ | |/
| * Merge branch '10.2' into 10.3Monty2019-09-031-0/+3
| |
* | MDEV-16188 Post review fixesIgor Babaev2019-02-141-0/+2
| | | | | | | | Also adjusted some test files.
* | Merge branch '10.4' into bb-10.4-mdev16188Igor Babaev2019-02-031-0/+1
|\ \ | |/
| * Merge branch '10.2' into 10.3Sergei Golubchik2019-01-031-0/+1
| |
* | MDEV-16188 Use in-memory PK filters built from range index scansIgor Babaev2019-02-031-0/+13
|/ | | | | | | | | | | | | | | | | | | | | | 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.
* Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-291-0/+823
View Lorry Controller Status