summaryrefslogtreecommitdiff
path: root/mysql-test/main/innodb_ext_key,off.rdiff
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-27036: resolve duplicated key issues of JSON tracing outputs:Sergei Krivonos2021-11-261-27/+27
| | | | | | | | | | | MDEV-27036: repeated "table" key resolve for print_explain_json MDEV-27036: duplicated keys in best_access_path MDEV-27036: Explain_aggr_filesort::print_json_members: resolve duplicated "filesort" member in Json object MDEV-27036: Explain_basic_join:: print_explain_json_interns fixed start_dups_weedout case for main.explain_json test
* Merge 10.4 into 10.5Marko Mäkelä2020-10-301-4/+6
|\
| * Try to stabilize main.innodb_ext_key,offMarko Mäkelä2020-10-301-0/+2
| | | | | | | | | | 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-22/+19
|\ \ | |/
| * MDEV-23991 fixup: Initialize the memoryMarko Mäkelä2020-10-301-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | 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-9/+0
| | | | | | | | | | | | | | 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-26/+23
| |\
* | | Merge 10.4 into 10.5Marko Mäkelä2020-09-041-8/+5
|/ /
* | Merge 10.3 into 10.4Marko Mäkelä2020-09-031-31/+34
|/
* Merge 10.2 into 10.3Marko Mäkelä2020-09-031-0/+295
View Lorry Controller Status