summaryrefslogtreecommitdiff
path: root/mysql-test/include
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* | | Mdev-10664 Add statuses about optimistic parallel replication stallsSachin Setiya2018-04-191-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In this commit we are adding three more status variable to SHOW SLAVE STATUS. Slave_DDL_Events and Slave_Non_Transactional_Events. Slave_DDL_Groups:- This status variable counts the occurrence of DDL statements Slave_Non_Transactional_Groups:- This variable count the occurrence of non-transnational event group. Slave_Transactional_Groups:- This variable count the occurrence of transnational event group. Patch Credit:- Kristian Nielsen
* | | Merge remote-tracking branch '10.2' into 10.3Vicențiu Ciorbaru2018-04-122-3/+6
|\ \ \ | |/ /
| * | Merge branch '10.1' into 10.2Vicențiu Ciorbaru2018-04-102-3/+6
| |\ \ | | |/
| | * MDEV-14616: WSREP has not yet prepared node for application use errorJan Lindström2018-04-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MariaDB adjustments. mysqltest.cc : Allow 12 error codes at --error wait_until_connected_again.inc: Replace numeric error codes with symbols mysqltest.test: Add error codes to test that tests too many errorcodes
| | * MW-405 Make sure wsrep is ready in wait_until_connected_again.incDaniele Sciascia2018-04-033-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | wait_until_connected_again issues 'SHOW STATUS' query repeatedly until mysqld replies without errors. However, SHOW STATUS is treated specially by wsrep in that it is allowed to proceed even if wsrep is not yet in ready state. As a consequence, after returning from wait_until_connected_again, wsrep may not be ready yet and subsequent queries may fail with error "1047 WSREP has not yet prepared node for application use". To avoid those errors, the patch includes wait_wsrep_ready.inc at the end of the wait_until_connected_again.
* | | Move mysql-test-run/extra/rpl_tests to suite/rpl/includeMichael Widenius2018-03-292-2/+2
| | | | | | | | | | | | | | | Renamed suite/rpl/include/rpl_sync.inc to rpl_sync_test.inc to remove clash with include/rpl_sync.inc
* | | Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-2956-27/+86
| | |
* | | Merge branch '10.2' into 10.3Sergei Golubchik2018-03-283-1/+9
|\ \ \ | |/ /
| * | Merge branch '10.1' into 10.2Sergei Golubchik2018-03-252-0/+8
| |\ \ | | |/
| | * MDEV-15409 make sure every sst script is tested in buildbotSergei Golubchik2018-03-232-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | galera SST tests have a debug part, but we don't want to limit them to fulltest2 builder. So, add support for test files that have a debug part: * add maybe_debug.inc and maybe_debug.combinations * 'debug' combination is run when debug is available * 'release' combination is run otherwise * test wraps debug parts in if($with_debug) { ... } * and creates ,debug.rdiff for debug results
| * | Merge remote-tracking branch 'origin/10.1' into 10.2Vicențiu Ciorbaru2018-03-161-1/+1
| |\ \ | | |/
| | * Galera MTR Tests: Modify mysqltest so that if a --let = `SELECT ...` query ↵Philip Stoev2018-03-121-1/+1
| | | | | | | | | | | | is interrupted, the test does not fail but the error is communicated to caller
| | * MDEV-14904 Backport innodb_default_row_formatMarko Mäkelä2018-03-072-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | InnoDB in Debian uses utf8mb4 as default character set since version 10.0.20-2. This leads to major pain due to keys longer than 767 bytes. MariaDB 10.2 (and MySQL 5.7) introduced the setting innodb_default_row_format that is DYNAMIC by default. These versions also changed the default values of the parameters innodb_large_prefix=ON and innodb_file_format=Barracuda. This would allow longer column index prefixes to be created. The original purpose of these parameters was to allow InnoDB to be downgraded to MySQL 5.1, which is long out of support. Every InnoDB version since MySQL 5.5 does support operation with the relaxed limits. We backport the parameter innodb_default_row_format to MariaDB 10.1, but we will keep its default value at COMPACT. This allows MariaDB 10.1 to be configured so that CREATE TABLE is less likely to encounter a problem with the limitation: loose_innodb_large_prefix=ON loose_innodb_default_row_format=DYNAMIC (Note that the setting innodb_large_prefix was deprecated in MariaDB 10.2 and removed in MariaDB 10.3.) The only observable difference in the behaviour with the default settings should be that ROW_FORMAT=DYNAMIC tables can be created both in the system tablespace and in .ibd files, no matter what innodb_file_format has been assigned to. Unlike MariaDB 10.2, we are not changing the default value of innodb_file_format, so ROW_FORMAT=COMPRESSED tables cannot be created without changing the parameter.
* | | MDEV-14829 Assertion `0' failed in Protocol::end_statement upon concurrent ↵Eugene Kosov2018-02-241-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | UPDATE vers_insert_history_row(): do not insert rows with zero or negative lifetime. mysql_update(): properly handle error from vers_insert_history_row()
* | | Merge bb-10.2-ext into 10.3Marko Mäkelä2018-02-151-1/+4
|\ \ \
| * \ \ Merge remote-tracking branch 'origin/10.2' into bb-10.2-extAlexander Barkov2018-02-081-1/+4
| |\ \ \ | | |/ /
| | * | Disabled galera_ist_progress at it always fails in 10.2Monty2018-02-071-1/+4
| | | |
* | | | Fixed failing tests rpl_semi_sync_skip_repl.testMichael Widenius2018-01-291-15/+0
| | | | | | | | | | | | | | | | Removed not used have_semisync_plugin.inc
* | | | cleanup: remove include/rpl_events.incbb-10.3-temporal-sergSergei Golubchik2018-01-131-159/+0
| | | | | | | | | | | | | | | | | | | | introduces 10 years ago, still included only once. no need to complicate debugging by unnecessary includes.
* | | | Merge bb-10.2-ext into 10.3Marko Mäkelä2018-01-055-563/+12
|\ \ \ \ | |/ / /
| * | | Merge remote-tracking branch 'origin/10.2' into bb-10.2-extMonty2018-01-055-563/+12
| |\ \ \ | | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: mysql-test/r/cte_nonrecursive.result mysql-test/suite/galera/r/galera_bf_abort.result mysql-test/suite/galera/r/galera_bf_abort_get_lock.result mysql-test/suite/galera/r/galera_bf_abort_sleep.result mysql-test/suite/galera/r/galera_enum.result mysql-test/suite/galera/r/galera_fk_conflict.result mysql-test/suite/galera/r/galera_insert_multi.result mysql-test/suite/galera/r/galera_many_indexes.result mysql-test/suite/galera/r/galera_mdl_race.result mysql-test/suite/galera/r/galera_nopk_bit.result mysql-test/suite/galera/r/galera_nopk_blob.result mysql-test/suite/galera/r/galera_nopk_large_varchar.result mysql-test/suite/galera/r/galera_nopk_unicode.result mysql-test/suite/galera/r/galera_pk_bigint_signed.result mysql-test/suite/galera/r/galera_pk_bigint_unsigned.result mysql-test/suite/galera/r/galera_serializable.result mysql-test/suite/galera/r/galera_toi_drop_database.result mysql-test/suite/galera/r/galera_toi_lock_exclusive.result mysql-test/suite/galera/r/galera_toi_truncate.result mysql-test/suite/galera/r/galera_unicode_pk.result mysql-test/suite/galera/r/galera_var_auto_inc_control_off.result mysql-test/suite/galera/r/galera_wsrep_log_conficts.result sql/field.cc sql/rpl_gtid.cc sql/share/errmsg-utf8.txt sql/sql_acl.cc sql/sql_parse.cc sql/sql_partition_admin.cc sql/sql_prepare.cc sql/sql_repl.cc sql/sql_table.cc sql/sql_yacc.yy
| | * | MDEV-14057 InnoDB GIS tests failMarko Mäkelä2018-01-045-563/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix and enable some of the tests; some remain disabled. The tests innodb_gis.rtree_old and innodb_gis.row_format duplicated some versions of the test main.gis-rtree. Instead of duplicating, source that test, in a new test innodb_gis.innodb_gis_rtree. Introduce innodb_row_format.combinations. Due to this, ROW_FORMAT=COMPRESSED will not be covered in some tests where it is covered in MySQL 5.7.
* | | | Merge bb-10.2-ext into 10.3Marko Mäkelä2018-01-041-8/+3
|\ \ \ \ | |/ / /
| * | | Merge 10.2 into bb-10.2-extMarko Mäkelä2018-01-031-8/+3
| |\ \ \ | | |/ /
| | * | Merge 10.1 into 10.2, with some MDEV-14799 fixupsmariadb-10.2.12Marko Mäkelä2018-01-031-8/+3
| | |\ \ | | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | trx_undo_page_report_modify(): For SPATIAL INDEX, keep logging updated off-page columns twice, so that the minimum bounding rectangle (MBR) will be logged. Avoiding the redundant logging would require larger changes to the undo log format. row_build_index_entry_low(): Handle SPATIAL_UNKNOWN more robustly, by refusing to purge the record from the spatial index. We can get this code when processing old undo log from 10.2.10 or 10.2.11 (the releases affected by MDEV-14799, which was a regression from MDEV-14051).
| | | * Merge 10.0 into 10.1Marko Mäkelä2018-01-021-8/+3
| | | |\
| | | | * Merge 5.5 into 10.0Marko Mäkelä2018-01-021-8/+3
| | | | |\
| | | | | * MDEV-14309 MTR tests require perl-Env which is not always in the default ↵Sergei Golubchik2017-12-271-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | installation * don't use Env module in tests, use $ENV{xxx} instead * collateral changes: ** $file in the error message was unset ** $file in the other error message was unset too :) ** source file arguments are conventionally upper-cased ** abort the test (die) on error, don't just echo/exit
* | | | | | Merge bb-10.2-ext into 10.3Marko Mäkelä2017-12-191-1/+4
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Follow-up to MDEV-13407 innodb.drop_table_background failed in buildbot with ↵Marko Mäkelä2017-12-191-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "Tablespace for table exists" 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.
* | | | | | Moved semisync from a plugin to normal serverMonty2017-12-184-76/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Part of MDEV-13073 AliSQL Optimize performance of semisync Did the following renames to match other similar variables key_ss_mutex_LOCK_binlog_ > key_LOCK_bing key_ss_cond_COND_binlog_send_ -> key_COND_binlog_send COND_binlog_send_ -> COND_binlog_send LOCK_binlog_ -> LOCK_binlog debian/mariadb-server-10.2.install does not install semisync libs.
* | | | | | Test cleanup related to MDEV-12501Vesa Pentti2017-12-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | * Removing unnecessary --plugin-maturity=unknown definitions from tests
* | | | | | Merge bb-10.2-ext into 10.3Marko Mäkelä2017-12-141-15/+0
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 10.2 into bb-10.2-extMarko Mäkelä2017-12-141-15/+0
| |\ \ \ \ \ | | |/ / / /
| | * | | | Re-remove the file kill_and_restart_mysqld.incMarko Mäkelä2017-12-141-15/+0
| | | | | |
* | | | | | Merge bb-10.2-ext into 10.3Marko Mäkelä2017-12-121-0/+14
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 10.2 into bb-10.2-extMarko Mäkelä2017-12-081-0/+14
| |\ \ \ \ \ | | |/ / / /
| | * | | | MDEV-14350 Index use with collation utf8mb4_unicode_nopad_ci on LIKE pattern ↵Alexander Barkov2017-12-081-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | with wrong results
* | | | | | MDEV-12501 -- set --maturity-level by defaultVesa Pentti2017-12-093-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Note: breaking change; since this commit, a plugin that has worked so far might get rejected due to plugin maturity * mariabackup is not affected (allows all plugins) * VERSION file defines SERVER_MATURITY, which defines the corresponding numeric value as SERVER_MATURITY_LEVEL in include/mysql_version.h * The default value for 'plugin_maturity' is SERVER_MATURITY_LEVEL - 1 * Logs a warning if a plugin has maturity lower than SERVER_MATURITY_LEVEL * Tests suppress the plugin maturity warning * Tests use --plugin-maturity=unknown by default so as not to fail due to the stricter plugin maturity handling
* | | | | | Merge bb-10.2-ext into 10.3Marko Mäkelä2017-12-063-8/+18
|\ \ \ \ \ \ | |/ / / / /
| * | | | | Merge 10.2 into bb-10.2-extMarko Mäkelä2017-12-063-8/+18
| |\ \ \ \ \ | | |/ / / /
View Lorry Controller Status