summaryrefslogtreecommitdiff
path: root/mysql-test/suite
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch '10.1' into 10.2Sergei Golubchik2017-02-1037-213/+565
|\
| * Minor test improvementNirbhay Choubey2017-01-313-1/+5
| |
| * MDEV-11945: Fix description for "max_statement_time" in --helpNirbhay Choubey2017-01-312-2/+2
| | | | | | | | max_statement_time also applies to non-SELECT queries.
| * MDEV-11817: Altering a table with more rows than ..Nirbhay Choubey2017-01-312-2/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | .. wsrep_max_ws_rows causes cluster to break when running Galera cluster in TOI mode Problem: While copying records to temporary table during ALTER TABLE, if there are more than wsrep_max_wsrep_rows records, the command fails. Fix: Since, the temporary table records are not placed into the binary log, wsrep_affected_rows must not be incremented. Added a test.
| * MDEV-10812 WSREP causes responses being sent to protocol commandsSachin Setiya2017-01-312-0/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | that must not send a response Problem:- When using wsrep (w/ galera) and issuing commands that can cause deadlocks, deadlock exception errors are sent in responses to commands such as close prepared statement and close connection which, by spec, must not send a response. Solution:- In dispatch_command, we will handle COM_QUIT and COM_STMT_CLOSE commands even in case of error. Patch Credit:- Jaka Močnik
| * Mdev-4774- Fix tests casesSachin Setiya2017-01-312-46/+51
| |
| * Merge 10.0 into 10.1 (test-only changes)Marko Mäkelä2017-01-2711-71/+25
| |\ | | | | | | | | | | | | Adjust the 10.1 tests innodb.doublewrite and innodb.101_compatibility in the same way.
| | * Clean up a few tests that kill the server.Marko Mäkelä2017-01-277-75/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | As noted in MDEV-8841, any test that kills the server must issue FLUSH TABLES, so that tables of crash-unsafe storage engines will not be corrupted. Consistently issue this statement after any call mtr.add_suppression() calls. Also, do not invoke shutdown_server directly, but use helpers instead.
| | * MDEV-11814 test fixMarko Mäkelä2017-01-272-9/+7
| | | | | | | | | | | | | | | | | | Do not kill the server after call mtr.add_suppression(), because the procedure modifies a crash-unsafe table, and we do not want to corrupt that table.
| | * MDEV-11233 CREATE FULLTEXT INDEX with a token longer than 127 bytesMarko Mäkelä2017-01-273-0/+261
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | crashes server This bug is the result of merging the Oracle MySQL follow-up fix BUG#22963169 MYSQL CRASHES ON CREATE FULLTEXT INDEX without merging the base bug fix: Bug#79475 Insert a token of 84 4-bytes chars into fts index causes server crash. Unlike the above mentioned fixes in MySQL, our fix will not change the storage format of fulltext indexes in InnoDB or XtraDB when a character encoding with mbmaxlen=2 or mbmaxlen=3 and the length of a word is between 128 and 84*mbmaxlen bytes. The Oracle fix would allocate 2 length bytes for these cases. Compatibility with other MySQL and MariaDB releases is ensured by persisting the used maximum length in the SYS_COLUMNS table in the InnoDB data dictionary. This fix also removes some unnecessary strcmp() calls when checking for the legacy default collation my_charset_latin1 (my_charset_latin1.name=="latin1_swedish_ci"). fts_create_one_index_table(): Store the actual length in bytes. This metadata will be written to the SYS_COLUMNS table. fts_zip_initialize(): Initialize only the first byte of the buffer. Actually the code should not even care about this first byte, because the length is set as 0. FTX_MAX_WORD_LEN: Define as HA_FT_MAXCHARLEN * 4 aka 336 bytes, not as 254 bytes. row_merge_create_fts_sort_index(): Set the actual maximum length of the column in bytes, similar to fts_create_one_index_table(). row_merge_fts_doc_tokenize(): Remove the redundant parameter word_dtype. Use the actual maximum length of the column. Calculate the extra_size in the same way as row_merge_buf_encode() does.
| * | Merge 10.0 into 10.1Marko Mäkelä2017-01-265-0/+274
| |\ \ | | |/
| | * MDEV-11814 Refuse innodb_read_only startup if crash recovery is neededMarko Mäkelä2017-01-262-0/+220
| | | | | | | | | | | | | | | | | | | | | | | | recv_scan_log_recs(): Remember if redo log apply is needed, even if starting up in innodb_read_only mode. recv_recovery_from_checkpoint_start_func(): Refuse innodb_read_only startup if redo log apply is needed.
| | * MDEV-4774 Strangeness with max_binlog_stmt_cache_size SettingsSachin Setiya2017-01-203-0/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem:- When setting max_binlog_stmt_cache_size=18446744073709547520 from either command line or .cnf file, server fails to start. Solution:- Added one more function eval_num_suffix_ull , which uses strtoull to get unsigned ulonglong from string. And getopt_ull calls this function instead of eval_num_suffix. Also changed previous eval_num_suffix to eval_num_suffix_ll to remain consistent.
| * | Revert "MDEV-7409 On RBR, extend the PROCESSLIST info to include at least ↵Sachin Setiya2017-01-252-141/+0
| | | | | | | | | | | | | | | | | | the name of the recently used table" This reverts commit 15f46d517435f3570e2c788349637a06d818a619.
| * | MDEV-7409 On RBR, extend the PROCESSLIST info to include at least the name ↵Sachin Setiya2017-01-232-0/+141
| | | | | | | | | | | | | | | | | | | | | of the recently used table When RBR is used, add the db name to db Field and table name to Status Field of the "SHOW FULL PROCESSLIST" command for SQL thread.
| * | MDEV-11838: Innodb-encryption-algorithm default should be != noneJan Lindström2017-01-193-2/+73
| | | | | | | | | | | | | | | | | | | | | Change default to zlib, this has effect only if user has explicitly requested page compression and then user naturally expects that pages are really compressed if they can be compressed.
| * | MDEV-11835: InnoDB: Failing assertion: free_slot != NULL onJan Lindström2017-01-193-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | restarting server with encryption and read-only buf0buf.cc: Temporary slots used in encryption was calculated by read_threads * write_threads. However, in read-only mode write_threads is zero. Correct way is to calculate (read_threads + write_threads) * max pending IO requests.
| * | Merge branch '10.0' into 10.1mariadb-10.1.21Sergei Golubchik2017-01-172-0/+96
| |\ \ | | |/
| | * Merge branch '5.5' into 10.0Sergei Golubchik2017-01-172-0/+96
| | |\
| | | * bugfix: Item_func_min_max stored thd internallySergei Golubchik2017-01-152-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was used for get_datetime_value() and for thd->is_error(). But in fact, get_datetime_value() never used thd argument, because the cache ptr argument was NULL. And thd->is_error() check was not needed at that place at all.
| | | * bugfix: cmp_item_row::alloc_comparators() allocated on the wrong arenaSergei Golubchik2017-01-152-7/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | it used current_thd->alloc() and allocated on the thd's execution arena, not on table->expr_arena. Remove THD::arena_for_cached_items that is temporarily set in update_virtual_fields(), and replaces THD arena in get_datetime_value(). Instead set THD arena to table->expr_arena for the whole duration of update_virtual_fields()
| | | * MDEV-9690 concurrent queries with virtual columns crash in temporal codeSergei Golubchik2017-01-152-0/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Item_func_le included Arg_comparator. Arg_comparator remembered the current_thd during fix_fields and used that value during execution to allocate Item_cache in get_datetime_value(). But for vcols fix_fields and val_int can happen in different threads. Same bug for Item_func_in using in_datetime or cmp_item_datetime, both also remembered current_thd at fix_fields() to use it later for get_datetime_value(). As a fix, these objects no longer remember the current_thd, and get_datetime_value() uses current_thd at run time. This should not increase the number of current_thd calls much, as Item_cache is created only once anyway.
| * | | MDEV-10956 Strict Password Validation Breaks Replication.Alexey Botchkov2017-01-172-0/+37
| | | | | | | | | | | | | | | | | | | | strict_password_validation variable now has no effect in the slave thread.
| * | | Merge remote-tracking branch 'origin/10.1' into 10.1Vicențiu Ciorbaru2017-01-171-14/+14
| |\ \ \
| * | | | Post merge review fixesVicențiu Ciorbaru2017-01-172-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove duplicate lines from tests * Use thd instead of current_thd * Remove extra wsrep_binlog_format_names * Correctly merge union patch from 5.5 wrt duplicate rows. * Correctly merge SELinux changes into 10.1
| * | | | Post merge fix sysvars_innodb for xtradbVicențiu Ciorbaru2017-01-171-0/+5
| | | | |
| * | | | Merge remote-tracking branch 'origin/10.1' into 10.1bb-10.1-vicentiu-galeraVicențiu Ciorbaru2017-01-1626-221/+427
| |\ \ \ \ | | | | | | | | | | | | | | | | | | Extra merge due to more extra commits during merge process
| * \ \ \ \ Merge remote-tracking branch '10.0-galera' into 10.1Vicențiu Ciorbaru2017-01-163-0/+4
| |\ \ \ \ \
| | * \ \ \ \ Merge tag 'mariadb-10.0.29' into 10.0-galeraNirbhay Choubey2017-01-1345-157/+518
| | |\ \ \ \ \
| | * | | | | | MDEV-11636 Extra persistent columns on slave always gets NULL in RBRSachin Setiya2016-12-282-0/+326
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem:- In replication if slave has extra persistent column then these column are not computed while applying write-set from master. Solution:- While applying row events from server, we will generate values for extra persistent columns.
| | * | | | | | MDEV-11490 Galera_3nodes test suite does not suppress Warnings.Sachin Setiya2016-12-211-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem:- While running individual tests of Galera_3nodes , We get warnings like '[Warning] WSREP: Could not open state file for reading: '. And because of this individual tests fails. Solution:- We change suite.pm of Galera_3nodes to supress these warnings.
| | * | | | | | MDEV-11479 Improved wsrep_dirty_readsSachin Setiya2016-12-144-4/+174
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tasks:- Changes in wsrep_dirty_reads variable 1.) Global + Session scope (Current: session-only) 2.) Can be set using command line. 3.) Allow all commands that do not change data (besides SELECT) 4.) Allow prepared Statements that do not change data 5.) Works with wsrep_sync_wait enabled
| | * | | | | | Revert "MDEV-11016 wsrep_node_is_ready() check is too strict"Sachin Setiya2016-12-142-29/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 52ea5ad865b4f6b4b37176296a3be0a716c5109a. # Conflicts: # mysql-test/suite/galera/r/galera_var_dirty_reads.result # mysql-test/suite/galera/t/galera_var_dirty_reads.test # sql/sql_parse.cc
| | * | | | | | Fix failing tests.Nirbhay Choubey2016-12-097-84/+60
| | | | | | | |
| | * | | | | | MDEV-11016 wsrep_node_is_ready() check is too strictSachinSetiya2016-12-012-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem:- The condition that checks for node readiness is too strict as it does not allow SELECTs even if these selects do not access any tables. For example,if we run SELECT 1; OR SELECT @@max_allowed_packet; Solution:- We need not to report this error when all_tables(lex->query_tables) is NULL:
| | * | | | | | Disable unstable galera_concurrent_ctas test.mariadb-galera-10.0.28Nirbhay Choubey2016-11-021-0/+1
| | | | | | | |
| * | | | | | | Merge branch '10.0' into 10.1Vicențiu Ciorbaru2017-01-1612-130/+102
| |\ \ \ \ \ \ \ | | | |_|_|_|/ / | | |/| | | | |
| | * | | | | | Merge branch '5.5' into 10.0Vicențiu Ciorbaru2017-01-145-3/+40
| | |\ \ \ \ \ \ | | | |_|/ / / / | | |/| | | | / | | | | |_|_|/ | | | |/| | |
| | | * | | | MDEV-11527 Virtual columns do not get along well with NO_ZERO_DATESergei Golubchik2017-01-122-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | don't check defaults for vcols
| | | * | | | MDEV-11706 Assertion `is_stat_field || !table || (!table->write_set || ↵Sergei Golubchik2017-01-113-3/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bitmap_is_set(table->write_set, field_index) || (table->vcol_set && bitmap_is_set(table->vcol_set, field_index)))' failed in Field_time::store_TIME_with_warning vcols and triggers. Revert 094f4cf77890c5a747a57cf2bed149b0b6933507, backport the correct fix (Table_triggers_list::mark_fields_used() not marking vcols) from 10.2.
| | * | | | | Merge branch 'bb-10.0-vicentiu' into 10.0mariadb-10.0.29Vicențiu Ciorbaru2017-01-126-122/+41
| | |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Extra merge commit due to intermediate commits pushed to 10.0 while merge was done.
| | | * \ \ \ \ Merge remote-tracking branch 'origin/5.5' into 10.0vicentiu2017-01-066-122/+41
| | | |\ \ \ \ \ | | | | |/ / / /
| | | | * | | | MDEV-11700 funcs_2.innodb_charset fails in buldbot on valgrind builder with ↵Elena Stepanova2017-01-051-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | timeout When the test is run as a part of the suite with valgrind, only allow it to be executed if --big-test is set. If the test is run by specifying its name explicitly, it will still be executed, even with valgrind without big-test, MTR has special logic for that
| | | | * | | | cleanup: rpl.rpl_row_mysqlbinlogSergei Golubchik2016-12-172-119/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | some trivial simplifications. drinking the ocean, one drop at a time
| | | | * | | | Follow-up for 02d153c7b9 (str2decimal: don't return a negative zero)Elena Stepanova2016-12-111-1/+0
| | | | | | | |
* | | | | | | | Adjust a test that is not supposed to crash.Marko Mäkelä2017-02-091-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is follow-up to commit 1293e5e59b6b412156ef8a78f762c0b099a10b50.
* | | | | | | | Relax assertions on shutdown after aborted startup.Marko Mäkelä2017-02-092-4/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A proper InnoDB shutdown after aborted startup was introduced in commit 81b7fe9d383bdf68a622b95384f067ed68ba342c. Also related to this is MDEV-11985, making read-only shutdown more robust. If startup was aborted, there may exist recovered transactions that were not rolled back. Relax the assertions accordingly.
* | | | | | | | Test fix for MDEV-6076 Persistent AUTO_INCREMENT for InnoDBMarko Mäkelä2017-02-082-4/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before killing the server, ensure that the redo log for the incomplete transaction is flushed, so that the AUTO_INCREMENT sequence will always be updated. Usually the INSERT transaction would not have persisted the sequence before the server was killed, but sometimes it could happen, causing result mismatch. Note: This test used to be called innodb_fts.innodb_fts_misc_debug.
* | | | | | | | Remove some more error log spam.Marko Mäkelä2017-02-0814-189/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not effectively set DEBUG_DBUG='d' by setting DEBUG_DBUG='-d,...'. Instead, restore the saved value of DEBUG_DBUG. Also, split the test innodb_fts.innodb_fts_misc_debug into innodb_fts.crash_recovery and innodb_fts.misc_debug, and enable these tests for --valgrind, the latter test for --embedded, and the former tests for the non-debug server.
* | | | | | | | MDEV-11974: MariaDB 10.2 encryption does not support spatial indexesJan Lindström2017-02-083-0/+118
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Encryption stores used key_version to FIL_PAGE_FILE_FLUSH_LSN_OR_KEY_VERSION (offset 26) field. Spatial indexes store RTREE Split Sequence Number (FIL_RTREE_SPLIT_SEQ_NUM) in the same field. Both values can't be stored in same field. Thus, current encryption implementation does not support encrypting spatial indexes. fil_space_encrypt(): Do not encrypt page if page type is FIL_PAGE_RTREE (this is required for background encryption innodb-encrypt-tables=ON). create_table_info_t::check_table_options() Do not allow creating table with ENCRYPTED=YES if table contains spatial index.
View Lorry Controller Status