summaryrefslogtreecommitdiff
path: root/mysql-test/suite
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-14101:Georg Richter2019-06-072-0/+14
| | | | | | | | | | | | | | | | | | | | | | Provide an option to select TLS protocol: Server and command line tools now support option --tls_version to specify the TLS version between client and server. Valid values are TLSv1.0, TLSv1.1, TLSv1.2, TLSv1.3 or a combination of them. E.g. --tls_version=TLSv1.3 --tls_version=TLSv1.2,TLSv1.3 In case there is a gap between versions, the lowest version will be used: --tls_version=TLSv1.1,TLSv1.3 -> Only TLSv1.1 will be available. If the used TLS library doesn't support the specified TLS version, it will use the default configuration. Limitations: SSLv3 is not supported. The default configuration doesn't support TLSv1.0 anymore. TLSv1.3 protocol currently is only supported by OpenSSL 1.1.0 (client and server) and GnuTLS 3.6.5 (client only).
* Minor Galera MTR test fixes (#1326)Daniele Sciascia2019-06-074-4/+5
|
* MDEV-19637 Crash on an SP variable assignment to a wrong subselectAlexander Barkov2019-05-302-0/+41
|
* Merge 10.3 into 10.4Marko Mäkelä2019-05-2938-134/+290
|\
| * Merge 10.2 into 10.3Marko Mäkelä2019-05-293-3/+3
| |\
| | * MDEV-19541: Suppress an error also on WindowsMarko Mäkelä2019-05-293-3/+3
| | |
| * | Merge 10.2 into 10.3Marko Mäkelä2019-05-2935-134/+275
| |\ \ | | |/
| | * MDEV-19541: Avoid infinite loop of reading a corrupted pageMarko Mäkelä2019-05-294-10/+20
| | | | | | | | | | | | | | | | | | row_search_mvcc(): Duplicate the logic of btr_pcur_move_to_next() so that an infinite loop can be avoided when advancing to the next page fails due to a corrupted page.
| | * Speed up buildbot by requiring --big-test for some slow testsMarko Mäkelä2019-05-2911-0/+22
| | |
| | * MDEV-19541: Add a forgotten test caseMarko Mäkelä2019-05-295-2/+75
| | | | | | | | | | | | | | | Also, --skip-innodb-buffer-pool-load-at-startup to avoid a crash in buf_load() due to loading pages that we are corrupting intentionally.
| | * MDEV-19587 innodb_force_recovery=5 crash on DROP SCHEMAMarko Mäkelä2019-05-282-15/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At higher levels of innodb_force_recovery, the InnoDB transaction subsystem will not be set up at all. At slightly lower levels, recovered transactions will not be rolled back, and DDL operations could hang due to locks being held at all. Let us consistently refuse all writes if the predicate high_level_read_only holds. We failed to refuse DROP TABLE and DROP DATABASE. (Refusing DROP TABLE is a partial backport from MDEV-19570 in the 10.5 branch.)
| | * Merge 10.1 into 10.2Marko Mäkelä2019-05-282-18/+26
| | |\
| | | * MDEV-17948 Assertion `thd_killed(thd) || !m_active_tranxs ..Andrei Elkin2019-05-242-17/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Simulation of a big-sized event in rpl.rpl_semi_sync_skip_repl did not clean up after itself so screw the last binlog event offset which could jump backwards. The test is refined to rotate a binlog file with simulation and use the next one for logics of the test incl master-slave synchonization.
| | | * MDEV-16021: galera mtr test galera_evs_suspect_timeout crashedJan Lindström2019-05-172-25/+44
| | | | | | | | | | | | | | | | | | | | Crash was timeout crash. Add correct waits for connections, wsrep sync waits and auto increment offset save and restore.
| | | * MDEV-13549: Timeout in wait_condition.inc for PROCESSLISTJan Lindström2019-05-173-29/+18
| | | | | | | | | | | | | | | | | | | | Use wsrep sync wait instead of unnecessary waits and correct slave setting.
| | | * MDEV-17061: Test failure on galera.galera_gcs_fc_limitJan Lindström2019-05-173-29/+29
| | | | | | | | | | | | | | | | | | | | | | | | Remove unnecessary sleeps and fix wait_condition to use wsrep_flow_control_paused i.e. we wait until flow control pauses a transaction on master.
| | * | MDEV-19541 InnoDB crashes when trying to recover a corrupted pageThirunarayanan Balathandayuthapani2019-05-284-12/+15
| | | | | | | | | | | | | | | | | | | | | | | | - Don't apply redo log for the corrupted page when innodb_force_recovery > 0. - Allow the table to be dropped when index root page is corrupted when innodb_force_recovery > 0.
| | * | Fixed monitor.test to handle statistics >= 10Monty2019-05-212-27/+21
| | | |
| | * | MDEV-17456 Malicious SUPER user can possibly change audit log configuration ↵Alexey Botchkov2019-05-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | without leaving traces. thread_pool_server_audit.result fixed.
| | * | MDEV-17456 Malicious SUPER user can possibly change audit log configuration ↵Alexey Botchkov2019-05-191-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | without leaving traces. Fix for the SET GLOBAL server_audit_loggin=on; added.
| | * | MDEV-16021: galera mtr test galera_evs_suspect_timeout crashedJan Lindström2019-05-172-25/+48
| | | | | | | | | | | | | | | | | | | | Crash was timeout crash. Add correct waits for connections, wsrep sync waits and auto increment offset save and restore.
| | * | MDEV-13549: Timeout in wait_condition.inc for PROCESSLISTJan Lindström2019-05-173-29/+18
| | | | | | | | | | | | | | | | | | | | Use wsrep sync wait instead of unnecessary waits and correct slave setting.
| | * | MDEV-17061: Test failure on galera.galera_gcs_fc_limitJan Lindström2019-05-173-29/+29
| | | | | | | | | | | | | | | | | | | | | | | | Remove unnecessary sleeps and fix wait_condition to use wsrep_flow_control_paused i.e. we wait until flow control pauses a transaction on master.
* | | | MDEV-18425: wsrep.mdev_10186: Test failure: "Result length mismatch" ↵Jan Lindström2019-05-272-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (@@GLOBAL.wsrep_provider) Remove unnecessary select of provider name as it could be anything and be located on different directories (i.e. it full name could be different).
* | | | Merge 10.3 into 10.4Marko Mäkelä2019-05-226-0/+80
|\ \ \ \ | |/ / /
| * | | MDEV-18136 Server crashes in Item_func_dyncol_create::prepare_argumentsAleksey Midenkov2019-05-202-0/+33
| | | | | | | | | | | | | | | | [Closes tempesta-tech/mariadb#572]
| * | | MDEV-18512 using DATETIME(6) as row_start/row_end crashes serverEugene Kosov2019-05-202-0/+16
| | | | | | | | | | | | | | | | Disallow DATETIME for SYSTEM VERSIONING tables.
| * | | MDEV-19486 Server crashes in row_upd or row_upd_del_mark_clust_rec on ↵Eugene Kosov2019-05-202-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | REPLACE into a versioned table row_insert_for_mysql(): InnoDB sets values for row_start and row_end. And this function used to return those values to server in ha_innobase::write_row(). This buggy behavior was removed. Also, a piece of code in this function was reformatted. upd_node_t::make_versioned_helper(): Assert that the preallocated size of the update vector is not exceeded.
* | | | MDEV-19535 sql_mode=ORACLE: 'SELECT INTO @var FOR UPDATE' does not lock the ↵Alexander Barkov2019-05-212-0/+54
| | | | | | | | | | | | | | | | table
* | | | MDEV-19524 Server crashes in Bitmap<64u>::is_clear_all / ↵Eugene Kosov2019-05-212-1/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Field_longstr::csinfo_change_allows_instant_alter compare_keys_but_name(): reorder checks to ensure that new_field->field != NULL inside Field::is_equal()
* | | | fix of Galera testOleksandr Byelkin2019-05-191-1/+2
| | | |
* | | | Merge branch '10.3' into 10.4Oleksandr Byelkin2019-05-1977-108/+1330
|\ \ \ \ | |/ / /
| * | | update a test result, followup fae6539ef72Sergei Golubchik2019-05-181-3/+3
| | | |
| * | | Merge branch '10.2' into 10.3Sergei Golubchik2019-05-173-6/+6
| |\ \ \ | | |/ /
| | * | restore the correct test resultSergei Golubchik2019-05-172-4/+4
| | | |
| | * | MDEV-13992 Implement JSON_MERGE_PATCH.Alexey Botchkov2019-05-171-2/+2
| | | | | | | | | | | | | | | | | | | | JSON_MERGE_PATCH implemented. Added JSON_MERGE_PRESERVE as a synonim for the JSON_MERGE.
| * | | MDEV-15458 Segfault in heap_scan() upon UPDATE after ADD SYSTEM VERSIONINGSergei Golubchik2019-05-178-9/+74
| | | | | | | | | | | | | | | | | | | | | | | | * Versioning tests support Closes #1043
| * | | MDEV-15408 Confusing error message upon ER_VERS_FIELD_WRONG_TYPE while ↵Eugene Kosov2019-05-172-1/+31
| | | | | | | | | | | | | | | | | | | | | | | | omitting UNSIGNED in BIGINT Improve diagnostics. Try to guess what type user tried to type.
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-05-162-0/+33
| |\ \ \ | | |/ /
| | * | MDEV-19485: Add a test caseMarko Mäkelä2019-05-162-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bug was introduced in MariaDB 10.4.0 by commit 0e5a4ac2532c64a545796c787354dc41d61d0e62 but it is good to have a regression test for this scenario in all applicable MariaDB versions. Cover the purge of an undo log record that was written before the completion of ADD SPATIAL INDEX.
| * | | A cleanup for MDEV-19468 Hybrid type expressions return wrong format for FLOATAlexander Barkov2019-05-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixing problems revealed by buildbot: - Fixing compilation failure on Windows - Recoding correct engines/iuds/r/insert_decimal.result
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-05-145-7/+106
| |\ \ \ | | |/ /
| | * | MDEV-19158: MariaDB 10.2.22 is writing duplicate entries into binary logSujatha2019-05-142-0/+101
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: ======== We have a Master/Master Setup on two servers, but are only writing to one of those servers (so it is essentially Master/Slave) We upgraded from 10.1.* to 10.2.22 last week and starting with the upgrade, we are getting duplicate key errors on the slave. BINLOG=mixed. Analysis: ========= This issue happens with LOCK TABLES and binlog_format=MIXED combination. When an UNSAFE statement is encountered in 'MIXED' mode, it is logged in the form of 'ROW' format. For all the tables that are part of LOCK TABLES list their table maps are written into the binary log. For each table in the list a check is done to see if 'check_table_binlog_row_based_done' flag is set or not. If it is not set a check process is initiated to see if table qualifies for row based binary logging or not and 'check_table_binlog_row_based_done' is set. This flag will be cleared at the time of closing thread tables. But there can be special cases where the LOCK TABLES contains more number of tables but the unsafe query is actually using subset of tables from LOCK TABLES list. For example: LOCK TABLES locks t1,t2,t3 but the unsafe statement makes use of only two tables t1,t3. In this case the 'check_table_binlog_row_based_done' flag is enabled for table 't2' while writing table map, but 'close_thread_tables' function call will not reset this flag. Since the flag is not cleared for table 't2' even a safe statement which used t2 will be logged in the form of row based format. This leads to an assert on debug builds and causes duplicate entries in release builds. In release builds a statement is logged in the form of both ROW and STATEMENT format. This causes the slave to fail with duplicate key error. Fix: === During 'close_thread_tables' when LOCK TABLE modes are active "ha_reset" is done for all the tables which were part of current statement. As mentioned in the example 'ha_reset' is called for tables 't1' and 't3'. This will clear the 'check_table_binlog_row_based_done' flag. At this point add a check for the rest of the tables to see if 'check_table_binlog_row_based_done' is enabled or not. If enabled clear the flag.
| | * | Merge branch '10.1' into 10.2Sujatha2019-05-143-7/+5
| | |\ \ | | | |/
| | | * MDEV-11095: rpl.rpl_row_mysqlbinlog test fails if row annotation enabledSujatha2019-05-141-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: ======= Whel rpl.rpl_row_mysqlbinlog test is executed as shown below it fails with result content mismatch. perl mtr rpl_row_mysqlbinlog --mysqld=--binlog-annotate-row-events=1 Analysis: ========= When row annotations are enabled the actual query is written into the binlog which helps users to understand the query, even when row based replication is enabled. For example: Simple insert in row based replication looks like shown below. #190402 16:31:27 server id 1 end_log_pos 526 Annotate_rows: #Q> insert into t values (10) #190402 16:31:27 server id 1 end_log_pos 566 Table_map: `test`.`t` mapped to number 19 # at 566 #190402 16:31:27 server id 1 end_log_pos 600 Write_rows: table id 19 flags: STMT_END_F BINLOG ' B0GjXBMBAAAAKAAAADYCAAAAABMAAAAAAAEABHRlc3QAAXQAAQMAAQ== B0GjXBcBAAAAIgAAAFgCAAAAABMAAAAAAAEAAf/+CgAAAA== '/*!*/; # at 600 The test creates some binary log events and redirects them into a SQL file. Executes RESET MASTER and sources the SQL file back on clean master and verifies that the data is available. Please refer following steps. ../client/mysqlbinlog ./var/mysqld.1/data/master-bin.000001 > test.sql ../client/mysql -uroot -S./var/tmp/mysqld.1.sock -Dtest < test.sql ../client/mysqlbinlog ./var/mysqld.1/data/master-bin.000001 -v > row.sql When the row based replication specific SQL file is sourced once again on master the newly generated binlog will treat the entire "BASE 64" encoded event as query and write it into the binary log. Output from 'row.sql': #Q> BINLOG ' #Q> B0GjXBMBAAAAKAAAADYCAAAAABMAAAAAAAEABHRlc3QAAXQAAQMAAQ== #Q> B0GjXBcBAAAAIgAAAFgCAAAAABMAAAAAAAEAAf/+CgAAAA== #190402 16:31:27 server id 1 end_log_pos 657 Table_map: `test`.`t` mapped to number 23 # at 657 #190402 16:31:27 server id 1 end_log_pos 691 Write_rows: table id 23 flags: STMT_END_F BINLOG ' B0GjXBMBAAAAKAAAAJECAAAAABcAAAAAAAEABHRlc3QAAXQAAQMAAQ== B0GjXBcBAAAAIgAAALMCAAAAABcAAAAAAAEAAQH+CgAAAA== ### INSERT INTO `test`.`t` ### SET ### @1=10 '/*!*/; # at 691 This is expected behaviour as we cannot extract query from BASE 64 encoded input. This causes more number of binary logs to be generated when the test is executed with row annotations. The following lines from test assumes that only two binary logs will contain entire data. --echo --- Test 4 Second Remote test -- ---exec $MYSQL_BINLOG --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000001 > $MYSQLTEST_VARDIR/tmp/remote.sql ---exec $MYSQL_BINLOG --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000002 >> $MYSQLTEST_VARDIR/tmp/remote.sql In a case when row annotations are enabled the data gets spread across four binary logs. As test uses only the first two binary log files, data available in other binary logs gets missed. Hence test fails with result content mismatch as less data is avaialble. Fix: ==== Use "-to-the-last" option of "mysqlbinlog" tool which will ensure that all the available binary log specific contents are included in .sql file.
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-05-144-0/+180
| |\ \ \ | | |/ /
| | * | Merge 10.1 into 10.2Marko Mäkelä2019-05-134-0/+180
| | |\ \ | | | |/
| | | * MDEV-19445 heap-use-after-free related to innodb_ft_aux_tableMarko Mäkelä2019-05-134-0/+175
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Try to fix the race conditions between SET GLOBAL innodb_ft_aux_table = ...; and access to the INFORMATION_SCHEMA tables that depend on this variable. innodb_ft_aux_table: Replaces fts_internal_tbl_name,fts_internal_tbl_name2. Just store the user-specified parameter as is. innodb_ft_aux_table_id: The table_id corresponding to SET GLOBAL innodb_ft_aux_table, or 0 if the table does not exist or does not contain FULLTEXT INDEX. If the table is renamed later, the INFORMATION_SCHEMA tables will continue to refer to the table. If the table is dropped or rebuilt, the INFORMATION_SCHEMA tables will not find the table.
| * | | Merge 10.2 into 10.3Marko Mäkelä2019-05-148-8/+8
| |\ \ \ | | |/ /
| | * | Merge 10.1 into 10.2Marko Mäkelä2019-05-138-8/+8
| | |\ \ | | | |/
View Lorry Controller Status