summaryrefslogtreecommitdiff
path: root/mysql-test/include
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-18144: ANALYZE for statement support for PK filtersGalina Shalygina2019-02-061-1/+1
| | | | | | | | | | | | ANALYZE and ANALYZE FORMAT=JSON structures are changed in the way that they show additional information when rowid filter is used: - r_selectivity_pct - the observed filter selectivity - r_buffer_size - the size of the rowid filter container buffer - r_filling_time_ms - how long it took to fill rowid filter container New class Rowid_filter_tracker was added. This class is needed to collect data about how rowid filter is executed.
* MDEV-16188 Post-merge corrections and adjustmentsIgor Babaev2019-02-041-2/+2
|
* Merge branch '10.4' into bb-10.4-mdev16188Igor Babaev2019-02-0320-19/+234
|\
| * SSL test fixesmariadb-10.4.2Sergei Golubchik2019-01-281-5/+2
| | | | | | | | | | | | | | | | | | * fix CRL tests to work * regenerate certificates to be at least 2048 bit (fixes buster and rhel8 in buildbot) * update generate-ssl-cert.sh to generate crl files * make all SSL tests to use certificates generated in generate-ssl-cert.sh, remove unused certificates
| * Galera4Brave Galera Crew2019-01-237-1/+117
| |
| * MDEV-7598 Lock user after too many password errorsVladislav Vaintroub2019-01-081-0/+13
| |
| * Merge 10.3 into 10.4Marko Mäkelä2018-12-181-2/+2
| |\
| | * Merge 10.2 into 10.3Marko Mäkelä2018-12-181-2/+2
| | |\
| | | * Merge 10.1 into 10.2Marko Mäkelä2018-12-171-2/+2
| | | |\
| | | | * MDEV-18021: Galera test galera_sst_mariabackup_table_options fails if ↵Jan Lindström2018-12-171-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | AES_CTR is not available Problem is that if you use bundled yassl AES_CTR is not supported. There is a way to detect that but as we really want to keep this test enabled did not add skip for missing support. Changed method to AES_CBC as there is no need to use AES_CTR.
| * | | | MDEV-17658 change the structure of mysql.user tableSergei Golubchik2018-12-125-2/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implement User_table_json. Fix scripts to use mysql.global_priv. Fix tests.
| * | | | more tests for mysql_install_db.exeSergei Golubchik2018-12-121-7/+12
| | | | |
| * | | | Combine GLOBAL and COMMIT namespaces into BACKUP namespace.Sergey Vojtovich2018-12-091-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Part of MDEV-5336 Implement LOCK FOR BACKUP Other things: - Added printing of MDL locks to DBUG.
| * | | | MDEV-17255: New optimizer defaults and ANALYZE TABLEVarun Gupta2018-12-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added to new values to the server variable use_stat_tables. The values are COMPLEMENTARY_FOR_QUERIES and PREFERABLY_FOR_QUERIES. Both these values don't allow to collect EITS for queries like analyze table t1; To collect EITS we would need to use the syntax with persistent like analyze table t1 persistent for columns (col1,col2...) index (idx1, idx2...) / ALL Changing the default value from NEVER to PREFERABLY_FOR_QUERIES.
| * | | | Merge 10.3 into 10.4Marko Mäkelä2018-11-262-0/+18
| |\ \ \ \ | | |/ / /
| | * | | Merge 10.2 into 10.3Marko Mäkelä2018-11-262-0/+18
| | |\ \ \ | | | |/ / | | | | | | | | | | | | | | | The test galera_sst_mariabackup_table_options was disabled, because the server refuses to start up due to wrong parameters.
| | | * | Merge remote-tracking branch 'origin/10.1' into 10.2Jan Lindström2018-11-212-0/+18
| | | |\ \ | | | | |/
| | | | * MDEV-17771: Add Galera ist and sst tests using mariabackupJan Lindström2018-11-212-0/+18
| | | | | | | | | | | | | | | | | | | | Add test case for encrypted and page compressed tables.
| * | | | Merge 10.3 into 10.4Marko Mäkelä2018-11-211-0/+4
| |\ \ \ \ | | |/ / /
| | * | | Merge 10.2 into 10.3Marko Mäkelä2018-11-201-0/+4
| | |\ \ \ | | | |/ /
| | | * | MDEV-17507 Make MTR tests work for builds without Aria for temporary tablesElena Stepanova2018-11-201-0/+4
| | | | | | | | | | | | | | | | | | | | Skip tests which expectedly fail when Aria is not used for temporary tables
* | | | | MDEV-16188 Use in-memory PK filters built from range index scansIgor Babaev2019-02-033-6/+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.
* | | | Merge 10.3 into 10.4mariadb-10.4.0Marko Mäkelä2018-11-081-1/+1
|\ \ \ \ | |/ / /
| * | | MDEV-14429 sql_safe_updates in my.cnf not workSergei Golubchik2018-11-061-1/+1
| | | | | | | | | | | | | | | | add a test case
* | | | Merge 10.3 into 10.4Marko Mäkelä2018-11-062-0/+18
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into 10.3Marko Mäkelä2018-11-062-0/+18
| |\ \ \ | | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | main.derived_cond_pushdown: Move all 10.3 tests to the end, trim trailing white space, and add an "End of 10.3 tests" marker. Add --sorted_result to tests where the ordering is not deterministic. main.win_percentile: Add --sorted_result to tests where the ordering is no longer deterministic.
| | * | Merge 10.1 into 10.2Marko Mäkelä2018-11-062-0/+18
| | |\ \ | | | |/
| | | * Merge branch '10.0' into 10.1Sergei Golubchik2018-10-302-0/+18
| | | |\
| | | | * MDEV-12547: InnoDB FULLTEXT index has too strict ↵Thirunarayanan Balathandayuthapani2018-10-162-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | innodb_ft_result_cache_limit max limit - Backported the MYSQL_SYSVAR_SIZE_T to 10.0 - The parameter innodb_ft_result_cache_limit was only 32 bits wide also on 64-bit systems. Make it size_t, so that it will be 64 bits on 64-bit systems. - Added a test case that show how innodb_ft_result_cache_limit variables behaves in 32bit and 64 bit system.
| | * | | Follow-up to MDEV-13407 innodb.drop_table_background failed in buildbot with ↵Marko Mäkelä2018-09-071-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "Tablespace for table exists" This is a backport of commit 88aff5f471d3d9ae8ecc2f909bcf5bd0ddd6aa7c. The InnoDB background DROP TABLE queue is something that we should really remove, but are unable to until we remove dict_operation_lock so that DDL and DML operations can be combined in a single transaction. Because the queue is not persistent, it is not crash-safe. We should in some way ensure that the deferred-dropped tables will be dropped after server restart. The existence of two separate transactions complicates the error handling of CREATE TABLE...SELECT. We should really not break locks in DROP TABLE. Our solution to these problems is to rename the table to a temporary name, and to drop such-named tables on InnoDB startup. Also, the queue will use table IDs instead of names from now on. check-testcase.test: Ignore #sql-ib*.ibd files, because tables may enter the background DROP TABLE queue shortly before the test finishes. innodb.drop_table_background: Test CREATE...SELECT and the creation of tables whose file name starts with #sql-ib. innodb.alter_crash: Adjust the recovery, now that the #sql-ib tables will be dropped on InnoDB startup. row_mysql_drop_garbage_tables(): New function, to drop all #sql-ib tables on InnoDB startup. row_drop_table_for_mysql_in_background(): Remove an unnecessary and misplaced call to log_buffer_flush_to_disk(). (The call should have been after the transaction commit. We do not care about flushing the redo log here, because the table would be dropped again at server startup.) Remove the entry from the list after the table no longer exists. If server shutdown has been initiated, empty the list without actually dropping any tables. They will be dropped again on startup. row_drop_table_for_mysql(): Do not call lock_remove_all_on_table(). Instead, if locks exist, defer the DROP TABLE until they do not exist. If the table name does not start with #sql-ib, rename it to that prefix before adding it to the background DROP TABLE queue.
* | | | | cleanup: get rid of a SQL warning in a testSergei Golubchik2018-10-311-1/+1
| | | | |
* | | | | Merge 10.3 into 10.4Marko Mäkelä2018-09-111-2/+14
|\ \ \ \ \ | |/ / / /
| * | | | Merge 10.2 into 10.3Marko Mäkelä2018-09-061-2/+14
| |\ \ \ \ | | |/ / /
| | * | | MyRocks: post-merge fixes part #5: make rocksdb.rocksdb_checksums test passSergei Petrunia2018-08-291-2/+14
| | | | |
* | | | | MDEV-15851 Stop creating mysql.host tableVladislav Vaintroub2018-08-162-2/+0
| | | | | | | | | | | | | | | | | | | | Changed bootstrap scripts, adjusted result files.
* | | | | Merge 10.3 into 10.4Marko Mäkelä2018-08-161-0/+15
|\ \ \ \ \ | |/ / / /
| * | | | Merge 10.2 into 10.3Marko Mäkelä2018-08-031-0/+15
| |\ \ \ \ | | |/ / /
| | * | | Merge 10.1 into 10.2Marko Mäkelä2018-08-021-0/+15
| | |\ \ \ | | | |/ /
| | | * | Merge branch '10.0' into bb-10.1-merge-sanjaOleksandr Byelkin2018-07-251-0/+15
| | | |\ \ | | | | |/
| | | | * MDEV-13118 Wrong results with LOWER and UPPER and subqueryAlexander Barkov2018-07-191-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This problem is similar to MDEV-10306. 1. Fixing Item_str_conv::val_str(String *str) to return the result in "str", and to use tmp_value only as a temporary buffer for args[0]->val_str(). The new code version now guarantees that the result is always returned in "str". The trick with copy_if_not_alloced() is not used any more. 2. The change #1 revealed the same problem in SUBSTRING_INDEX(), so some tests with combinations of UPPER()/LOWER() and SUBSTRING_INDEX() started to fail. Fixing Item_func_substr_index::val_str() the same way, to return the result in "str" and use tmp_value as a temporary buffer for args[0]->val_str().
* | | | | MDEV-16421 Make system tables crash safeMichael Widenius2018-08-143-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make all system tables in mysql directory of type engine=Aria Privilege tables are using transactional=1 Statistical tables are using transactional=0, to allow them to be quickly updated with low overhead. Help tables are also using transactional=0 as these are only updated at init time. Other changes: - Aria store engine is now a required engine - Update comment for Aria tables to reflect their new usage - Fixed that _ma_reset_trn_for_table() removes unlocked table from transaction table list. This was needed to allow one to lock and unlock system tables separately from other tables, for example when reading a procedure from mysql.proc - Don't give a warning when using transactional=1 for engines that is using transactions. This is both logical and also to avoid warnings/errors when doing an alter of a privilege table to InnoDB. - Don't abort on warnings from ALTER TABLE for changes that would be accepted by CREATE TABLE. - New created Aria transactional tables are marked as not movable (as they include create_rename_lsn). - bootstrap.test was changed to kill orignal server, as one can't anymore have two servers started at same time on same data directory and data files. - Disable maria.small_blocksize as one can't anymore change aria block size after system tables are created. - Speed up creation of help tables by using lock tables. - wsrep_sst_resync now also copies Aria redo logs.
* | | | | MDEV-11953: support of brackets in UNION/EXCEPT/INTERSECT operationsOleksandr Byelkin2018-07-041-1/+1
|/ / / /
* | | | Merge 10.2 into 10.3Marko Mäkelä2018-06-182-1/+30
|\ \ \ \ | |/ / /
| * | | MDEV-15352 AUTO_INCREMENT breaks after updating a column value to a negative ↵Alexander Barkov2018-06-141-0/+29
| | | | | | | | | | | | | | | | number
| * | | Add missed change from 7ffa82b03c8da12062223d5e332e972d6f828d44Vicențiu Ciorbaru2018-06-111-1/+1
| | | |
* | | | cleanup: include/have_rbr_triggers.incSergei Golubchik2018-05-121-5/+0
| | | | | | | | | | | | | | | | | | | | this is always enabled now, no need for a conditional
* | | | Merge 10.2 into 10.3Marko Mäkelä2018-04-241-2/+32
|\ \ \ \ | |/ / /
| * | | Merge 10.1 into 10.2Marko Mäkelä2018-04-241-2/+32
| |\ \ \ | | |/ /
| | * | MDEV-15948 Followup commitDaniele Sciascia2018-04-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Increased timeout counter in galera_wait_ready.inc * Replaced useless include/wait_until_ready.inc after start_mysqld.inc in galera_st_*.inc with wait_condition on cluster size.
| | * | MDEV-15948 Fix error "Lost connection to MySQL server..." in test ↵Daniele Sciascia2018-04-201-2/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | galera_sst_mysqldump Test galera_sst_mysqldump often fails with error "2013: Lost connection to MySQL server during query". The connection is lost after the test restart one of the nodes. This happens because the server closes client connections if it is joining a cluster through SST method mysqldump. On unlucky runs of the test it is possible that mysqld is restarted, and then mtr client is disconnected while it tries to determine if galera is ready before going on with the test. This patch rewrites galera_wait_ready.inc so that it is immune to being disconnected.
View Lorry Controller Status