summaryrefslogtreecommitdiff
path: root/mysql-test/suite
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.2 into 10.3Marko Mäkelä2018-11-262-0/+18
|\
| * MDEV-17831 TRUNCATE TABLE removes ROW_FORMAT=COMPRESSEDMarko Mäkelä2018-11-262-0/+18
| | | | | | | | | | | | | | | | | | | | | | If a table had a KEY_BLOCK_SIZE attribute, but no ROW_FORMAT, it would be created as ROW_FORMAT=COMPRESSED in InnoDB. However, TRUNCATE TABLE would lose the KEY_BLOCK_SIZE attribute and create the table with the innodb_default_row_format (DYNAMIC). This is a regression that was introduced by MDEV-13564. update_create_info_from_table(): Copy also KEY_BLOCK_SIZE.
* | Merge 10.2 into 10.3Marko Mäkelä2018-11-2632-128/+2376
|\ \ | |/ | | | | | | The test galera_sst_mariabackup_table_options was disabled, because the server refuses to start up due to wrong parameters.
| * MDEV-17816 Crash in TRUNCATE TABLE when table creation failsMarko Mäkelä2018-11-262-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The error handling in the MDEV-13564 TRUNCATE TABLE was broken when an error occurred during table creation. row_create_index_for_mysql(): Do not drop the table on error. fts_create_one_common_table(), fts_create_one_index_table(): Do drop the table on error. create_index(), create_table_info_t::create_table(): Let the caller handle the index creation errors. ha_innobase::create(): If create_table_info_t::create_table() fails, drop the incomplete table, roll back the transaction, and finally return an error to the caller.
| * MDEV-17804: Galera tests cause mysql_socket.h:738: inline_mysql_socket_send: ↵Jan Lindström2018-11-221-4/+15
| | | | | | | | | | | | | | Assertion `mysql_socket.fd != -1' failed. Do not do end of statement logic if thd is already killed as socket is already closed.
| * MDEV-17801: Galera test failure on galera_var_reject_queriesJan Lindström2018-11-222-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem was that controlling connection i.e. connection that executed the query SET GLOBAL wsrep_reject_queries = ALL_KILL; was also killed but server would try to send result from that query to controlling connection resulting a assertion mysqld: /home/jan/mysql/10.2-sst/include/mysql/psi/mysql_socket.h:738: inline_mysql_socket_send: Assertion `mysql_socket.fd != -1' failed. as socket was closed when controlling connection was closed. wsrep_close_client_connections() Do not close controlling connection and instead of wsrep_close_thread() we do now soft kill by THD::awake wsrep_reject_queries_update() Call wsrep_close_client_connections using current thd.
| * MDEV-15522: Change galera suite MTR tests to use mariabackup instead of ↵Jan Lindström2018-11-221-1/+2
| | | | | | | | | | | | xtrabackup Disable galera_3nodes tests using xtrabackup.
| * MDEV-15522: Change galera suite MTR tests to use mariabackup instead of ↵Jan Lindström2018-11-221-0/+7
| | | | | | | | | | | | xtrabackup Disable galera tests using xtrabackup.
| * MDEV-17771: Add Galera ist and sst tests using mariabackupJan Lindström2018-11-228-8/+97
| | | | | | | | Record result files for 10.2.
| * Merge remote-tracking branch 'origin/10.1' into 10.2Jan Lindström2018-11-2124-110/+2232
| |\
| | * MDEV-17771: Add Galera ist and sst tests using mariabackupJan Lindström2018-11-214-0/+1221
| | | | | | | | | | | | Add test case for encrypted and page compressed tables.
| | * Add missing .rdiff file to test galera_sst_xtrabackup-v2_data_dirJan Lindström2018-11-201-0/+103
| | | | | | | | | | | | for debug build.
| | * MDEV-17771: Add Galera ist and sst tests using mariabackupJan Lindström2018-11-197-263/+211
| | | | | | | | | | | | | | | | | | Remove unnecessary have_debug requirement, record results using release build and create .rdiff file for debug builds where needed.
| | * fiexed debug build failure of galera_ist_mariabackup_innodb_flush_logszdrav12018-11-192-0/+110
| | |
| | * fiexed debug build failure of galera_ist_mariabackup testzdrav12018-11-192-0/+111
| | |
| | * added galera_ist_mariabackup_innodb_flush_logs testzdrav12018-11-193-0/+122
| | |
| | * fixed the test comments of galera_sst_mariabackup_encrypt_with_key testzdrav12018-11-191-2/+2
| | |
| | * added test galera_sst_mariabackup_encrypt_with_key; corrected path to ↵zdrav12018-11-195-0/+29
| | | | | | | | | | | | galera_ist_mariabackup test
| | * added test case galera_ist_mariabackupzdrav12018-11-193-0/+307
| | |
| | * added galera_autoinc_sst_mariabackup testzdrav12018-11-193-0/+155
| | |
| | * MDEV-16890: Galera test failure on galera_sst_mysqldump_with_keyJan Lindström2018-11-192-97/+106
| | | | | | | | | | | | | | | Record .rdiff file for debug build and record .result file using product build.
| | * MDEV-13881: galera.partition failed in buildbot with wrong resultJan Lindström2018-11-173-13/+20
| | | | | | | | | | | | Add proper wait conditions to second node before continuing test.
* | | Merge 10.2 into 10.3Marko Mäkelä2018-11-203-0/+4
|\ \ \ | |/ /
| * | MDEV-17507 Make MTR tests work for builds without Aria for temporary tablesElena Stepanova2018-11-203-0/+4
| | | | | | | | | | | | Skip tests which expectedly fail when Aria is not used for temporary tables
* | | Merge 10.2 into 10.3Marko Mäkelä2018-11-194-1/+125
|\ \ \ | |/ /
| * | Merge branch '10.1' into 10.2Oleksandr Byelkin2018-11-152-0/+117
| |\ \ | | |/
| | * Merge branch '10.0' into 10.1Oleksandr Byelkin2018-11-152-0/+117
| | |\
| | | * Merge branch '5.5' into 10.0Oleksandr Byelkin2018-11-152-0/+117
| | | |\
| | | | * MDEV-17724 Wrong result for BETWEEN 0 AND 18446744073709551615Alexander Barkov2018-11-152-0/+117
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fix for "MDEV-17698 MEMORY engine performance regression" previously fixed this problem. - Adding the test for MDEV-17724 - Re-recording wrong results for tests: * engines/iuds/r/insert_number * engines/iuds/r/update_delete_number which started to fail since MDEV-17698
| * | | | MDEV-17645 innodb.log_file_name_debug does not clean up after itselfMarko Mäkelä2018-11-082-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test innodb.log_file_name_debug failed to ensure that the bogus redo log record that its debug injection emitted would be consumed by a redo log checkpoint before running a subsequent test, which could perform crash recovery. Add an extra shutdown to ensure that a redo log checkpoint is generated. In this way, the following will succeed: ./mtr --no-reorder innodb.log_file_name_debug innodb.read_only_recovery
* | | | | Fix test result.Vladislav Vaintroub2018-11-151-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in 10.3, AWS encryption key was loaded during recovery, by the innodb purge thread, therefore no note "loaded key" was written by the foreground thread.
* | | | | MDEV-17278 CURSOR FOR LOOP - ERROR: unexpected end of stream, read 0 bytes ↵Alexander Barkov2018-11-142-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (SERVER CRASH) sp_instr_cursor_copy_struct::exec_core() created TYPELIBs on a wrong mem_root, the one which is initialized in sp_head::execute(), this code: /* init per-instruction memroot */ init_sql_alloc(&execute_mem_root, "per_instruction_memroot", MEM_ROOT_BLOCK_SIZE, 0, MYF(0)); This memory root cleans up after every sp_instr_xxx executed, so later sp_instr_cfetch::execute() tried to use already freed and trashed memory. Changing sp_instr_cursor_copy_struct::exec_core() to call tmp.export_structure() inside this block (not outside of it): thd->set_n_backup_active_arena(thd->spcont->callers_arena, &current_arena); ... thd->restore_active_arena(thd->spcont->callers_arena, &current_arena); So now TYPELIBs created by sp_instr_cursor_copy_struct::exec_core() are still available and valid when sp_instr_cfetch::execute() is called. They are freed at the end of dispatch_command() corresponding to the "CALL p1" statement.
* | | | | MDEV-17253 Oracle compatibility: The REVERSE key word for FOR loop behaves ↵Alexander Barkov2018-11-134-24/+125
| | | | | | | | | | | | | | | | | | | | incorrectly
* | | | | MDEV-14429 sql_safe_updates in my.cnf not workSergei Golubchik2018-11-132-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | update test results for embedded followup for 564a63b5a35 and 89a87e8e422
* | | | | MDEV-17693 Shift/reduce conflicts for NAMES,ROLE,PASSWORD in the ↵Alexander Barkov2018-11-132-0/+136
| | | | | | | | | | | | | | | | | | | | option_value_no_option_type grammar
* | | | | MDEV-17666 sql_mode=ORACLE: Keyword ELSEIF should not be reservedAlexander Barkov2018-11-122-0/+37
| | | | |
* | | | | A join patch for MDEV-17660 and MDEV-17661Alexander Barkov2018-11-102-0/+91
| | | | | | | | | | | | | | | | | | | | | | | | | MDEV-17660 sql_mode=ORACLE: Some keywords do not work as label names: history, system, versioning, without MDEV-17661 Add sql_mode specific tokens for the keyword DECODE
* | | | | MDEV-13134: Remove an orphan .inc fileMarko Mäkelä2018-11-091-33/+0
| | | | |
* | | | | MDEV-17387 MariaDB Server giving wrong error while executing select query ↵Alexander Barkov2018-11-094-0/+168
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from procedure Changing the way how a cursor is opened to fetch its structure only, e.g. for a cursor FOR loop record variable. The old methods with setting thd->lex->limit_rows_examined to an Item_uint(0) was not reliable and could push these messages into diagnostics area: The query examined at least 1 rows, which exceeds LIMIT ROWS EXAMINED (0) The new method should be more reliable, as it completely prevents the call of do_select() in JOIN::exec_inner() during the cursor structure discovery, so the execution of the cursor SELECT query returns immediately after the preparation step (when the result row structure becomes known), without even entering the code that fetches the result rows.
* | | | | Merge 10.2 into 10.3Marko Mäkelä2018-11-081-1/+0
|\ \ \ \ \ | |/ / / /
| * | | | MDEV-14528 followup.Andrei Elkin2018-11-071-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There was a failure in rpl_delayed_slave after recent MDEV-14528 commit. The parallel applier should not set its Relay_log::last_master_timestamp from Format-descriptor log event. The latter may reflect a deep past so Seconds-behind-master will be computed through it and displayed all time while the first possibly "slow" group of events is executed. The main MDEV-14528 is refined, rpl_delayed_slave now passes also in the parallel mode.
* | | | | Merge an .inc file to .testMarko Mäkelä2018-11-072-95/+93
| | | | |
* | | | | MDEV-13134: Merge tests to innodb.alter_algorithmMarko Mäkelä2018-11-0712-284/+348
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove the separate test innodb.alter_instant, because it can be easily mistaken for innodb.instant_alter, which in turn is covering various instant ALTER TABLE operations.
* | | | | Merge 10.2 into 10.3Marko Mäkelä2018-11-075-0/+73
|\ \ \ \ \ | |/ / / /
| * | | | MDEV-14528: Disable a failing testMarko Mäkelä2018-11-071-0/+1
| | | | |
| * | | | Merge 10.1 into 10.2Marko Mäkelä2018-11-072-0/+61
| |\ \ \ \ | | |/ / /
| | * | | MDEV-17230: encryption_key_id from alter is ignored by encryption threadsJan Lindström2018-11-062-0/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Background: Used encryption key_id is stored to encryption metadata i.e. crypt_data that is stored on page 0 of the tablespace of the table. crypt_data is created only if implicit encryption/not encryption is requested i.e. ENCRYPTED=[YES|NO] table option is used fil_create_new_single_table_tablespace on fil0fil.cc. Later if encryption is enabled all tables that use default encryption mode (i.e. no encryption table option is set) are encrypted with default encryption key_id that is 1. See fil_crypt_start_encrypting_space on fil0crypt.cc. ha_innobase::check_table_options() If default encryption is used and encryption is disabled, you may not use nondefault encryption_key_id as it is not stored anywhere.
| * | | | MDEV-14528 Track master timestamp in case rolling back to serial replicationIgor Mazur2018-11-062-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When replicated events are from Master unaware of MariaDB GTID their handling by the Parallel slave misses Seconds_Behind_Master updating. In the bug condition the Show-Slave-Status' field remains unchanged. Because in such case event execution is sequential the bug is fixed with deploying the same logics as in the explicit single-threaded mode with is to set Relay_log_event::last_master_timestamp member early at the end of event reading from the relay log.
* | | | | MDEV-14429 sql_safe_updates in my.cnf not workVladislav Vaintroub2018-11-061-1/+1
| | | | |
* | | | | Merge 10.2 into 10.3Marko Mäkelä2018-11-0661-156/+1805
|\ \ \ \ \ | |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
View Lorry Controller Status