summaryrefslogtreecommitdiff
path: root/mysql-test/suite/sys_vars
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.1 into 10.2Marko Mäkelä2020-06-064-24/+24
|\
| * MDEV-22715: SIGSEGV in radixsort_for_str_ptr and in native_compare/my_qsort2 ↵Varun Gupta2020-06-054-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | (optimized builds) For DECIMAL[(M[,D])] datatype max_sort_length was not being honoured which was leading to buffer overflow while making the sort key. The fix to this problem would be to create sort keys for decimals with atmost max_sort_key bytes Important: The minimum value of max_sort_length has been raised to 8 (previously was 4), so fixed size datatypes like DOUBLE and BIGINIT are not truncated for lower values of max_sort_length.
* | Merge 10.1 into 10.2Marko Mäkelä2020-05-201-1/+1
|\ \ | |/
| * MDEV-22258 Limit innodb_encryption_threads to 255Marko Mäkelä2020-05-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For no good reason, innodb_encryption_threads was limited to 4,294,967,295. Expectedly, the server would crash if such an insane value was specified. Let us limit the maximum to 255. The encryption threads are not doing much useful work. They are basically only dirtying pages by performing dummy writes via the redo log. The encryption key rotation or the in-place addition or removal of encryption will take place in the page cleaner. In a quick test on a 20-core CPU (40 threads in total), the sweet spot on an otherwise idle server seemed to be innodb_encryption_threads=16 for the test encryption.encrypt_and_grep. The new limit 255 should be more than enough for even bigger servers.
* | MDEV-21336 Memory leaks related to innodb_debug_syncMarko Mäkelä2020-05-141-12/+0
| | | | | | | | | | | | | | | | | | | | This essentially reverts commit b393e2cb0c079b30563dcc87a62002c9c778643c. The leak might have been fixed, but because the DEBUG_SYNC instrumentation for InnoDB purge threads was reverted in 10.5 commit 5e62b6a5e06eb02cbde1e34e95e26f42d87fce02 as part of introducing a thread pool, it is easiest to revert the entire change.
* | Merge 10.1 into 10.2Marko Mäkelä2020-05-131-1/+1
|\ \ | |/
| * MDEV-22501 Various issues when using --innodb-data-file-size-debug=-1Marko Mäkelä2020-05-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Let us limit the maximum value of the debug parameter innodb_data_file_size to 256 MiB. It is only being used in the test innodb.log_data_file_size, and the size of the system tablespace should never exceed some 70 MiB in ./mtr. Thus, 256 MiB should be a reasonable limit. The fact that negative values that are passed to unsigned parameters wrap around to the maximum value appears to be a regression due to commit 18ef02b04dfae21148c7397d088c7ffdfcd23c4e and has been filed as bug MDEV-22219.
* | Merge 10.1 into 10.2Marko Mäkelä2020-04-282-4/+4
|\ \ | |/
| * InnoDB 5.6.48Marko Mäkelä2020-04-283-3/+3
| |
| * XtraDB 5.6.47-87.0Marko Mäkelä2020-04-272-2/+2
| | | | | | | | | | | | | | The only change is a change of the version number. As noted in commit 02af6278fb7c7889a02d617eb23e82fe7967abd7 there were no changes to InnoDB between MySQL 5.6.46 and 5.6.47 either.
| * sysvars_server_* tests need to have performance schema enabledVicențiu Ciorbaru2020-04-131-0/+1
| | | | | | | | | | Tests will fail otherwise. Backport change from: 867809f23a8f09b1ac0aa8f9212ac8afd572efc
* | MDEV-20604: Duplicate key value is silently truncated to 64 characters in ↵Oleksandr Byelkin2020-04-0110-23/+23
| | | | | | | | | | | | print_keydup_error Added indication of truncated string for "s" and "M" formats
* | MDEV-18027: Running out of file descriptors and eventual crashOleksandr Byelkin2020-02-051-1/+1
| | | | | | | | For automatic number of opened files limit take into account number of table instances for table cache
* | MDEV-21360 save/restore debud_dbug instead of total reset at the end of the testAlice Sherepa2020-01-212-37/+37
| |
* | Merge branch '10.1' into 10.2Oleksandr Byelkin2020-01-202-4/+4
|\ \ | |/
| * InnoDB 5.6.47 and XtraDB 5.6.46-86.2Marko Mäkelä2020-01-173-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The only change is a change of the version number. In MySQL 5.6.46, the copyright comments in a number of files were changed in mysql/mysql-server@f1a006ece7521cb02f9b961e6fad04d12ddfbab3 but there was no functional change to InnoDB code. This was also reflected by XtraDB. We are not changing the copyright comments in MariaDB Server for now. Between MySQL 5.6.46 and 5.6.47, InnoDB was not changed at all. Actually, we had forgotten to update the InnoDB version number to 5.6.46. With this change, we are updating InnoDB from 5.6.45 to 5.6.47 and XtraDB from 5.6.45-86.1 to 5.6.46-86.2.
* | MDEV-21360 global debug_dbug pre-test value restoration issuesAlice Sherepa2020-01-152-6/+6
| |
* | Cleanup test sys_vars.innodb_buffer_pool_size_basicMarko Mäkelä2019-12-102-13/+2
| | | | | | | | | | When using huge pages, the innodb_buffer_pool_size cannot necessarily be restored. Simplify things by restarting the server.
* | MDEV-14482 - Cache line contention on ut_rnd_interval()Marko Mäkelä2019-12-102-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | InnoDB RNG maintains global state, causing otherwise unnecessary bus traffic. Even worse, this is cross-mutex traffic. That is, different mutexes suffer from contention. Fixed delay of 4 was verified to give best throughput by OLTP update index and read-write benchmarks on Intel Broadwell (2/20/40) and ARM (1/46/46). This is a backport of ce0479006523bc72ed6abb703bd1f87ff256fd8a from MariaDB Server 10.3.
* | Merge branch '10.1' into 10.2Oleksandr Byelkin2019-10-302-2/+2
|\ \ | |/
| * XtraDB 5.6.45-86.1Marko Mäkelä2019-10-302-2/+2
| |
* | MDEV-20864 Introduce debug option innodb_change_buffer_dumpMarko Mäkelä2019-10-191-0/+12
| | | | | | | | | | | | | | To diagnose a hang in slow shutdown (innodb_fast_shutdown=0), let us introduce a Boolean startup option in debug builds that will cause the contents of the InnoDB change buffer to be dumped to the server error log at startup.
* | MDEV-20850 Merge new release of InnoDB 5.7.28 to 10.2Marko Mäkelä2019-10-171-5/+0
| |
* | Fix CMAKE_BUILD_TYPE=DebugMarko Mäkelä2019-10-111-0/+12
| | | | | | | | | | | | | | | | Remove unused variables and type mismatch that was introduced in commit b393e2cb0c079b30563dcc87a62002c9c778643c Also, fix a typo in the documentation of the parameter, and update the test.
* | Merge 10.1 into 10.2Marko Mäkelä2019-09-112-31/+11
|\ \ | |/
| * MDEV-17683 sys_vars.delayed_insert_limit_func fails in buildbot with wrong ↵Alexey Botchkov2019-09-032-33/+11
| | | | | | | | | | | | result. Test fixed to be deterministic.
* | MDEV-19514 preparation: Remove innodb_change_buffering_debug=2Marko Mäkelä2019-09-093-5/+10
| | | | | | | | | | | | | | | | | | The setting innodb_change_buffering_debug=2 was supposed to inject a crash during change buffer merge. There is no public test for that functionality, and even if there were, it would be better to use DEBUG_SYNC to halt the thread that does change buffer merge, force a redo log flush from another thread, and finally kill the server externally.
* | Updated mtr files to support different compiled in optionsMonty2019-09-0195-5351/+2204
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows one to run the test suite even if any of the following options are changed: - character-set-server - collation-server - join-cache-level - log-basename - max-allowed-packet - optimizer-switch - query-cache-size and query-cache-type - skip-name-resolve - table-definition-cache - table-open-cache - Some innodb options etc Changes: - Don't print out the value of system variables as one can't depend on them to being constants. - Don't set global variables to 'default' as the default may not be the same as the test was started with if there was an additional option file. Instead save original value and reset it at end of test. - Test that depends on the latin1 character set should include default_charset.inc or set the character set to latin1 - Test that depends on the original optimizer switch, should include default_optimizer_switch.inc - Test that depends on the value of a specific system variable should set it in the test (like optimizer_use_condition_selectivity) - Split subselect3.test into subselect3.test and subselect3.inc to make it easier to set and reset system variables. - Added .opt files for test that required specfic options that could be changed by external configuration files. - Fixed result files in rockdsb & tokudb that had not been updated for a while.
* | Fixed issues found by valgrindMonty2019-08-122-37/+6
| | | | | | | | | | | | | | | | | | - mysqltest didn't free read_command_buf - wait_for_slave_param did write different things to the log if valgrind was used. - Table open cache should not write the initial variable value as it can depend on the configuration or if valgrind is used - A variable in GetResult was used uninitalized
* | MDEV-20060: Failing assertion: srv_log_file_size <= 512ULL << 30 while ↵Vlad Lesin2019-08-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | preparing backup The general reason why innodb redo log file is limited by 512G is that log_block_convert_lsn_to_no() returns value limited by 1G. But there is no need to have unique log block numbers in log group. The fix removes 512G limit and limits log group size by (uint32_t maximum value) * (minimum page size), which, in turns, can be removed if fil_io() is no longer used for innodb redo log io.
* | MDEV-20133 Merge new release of InnoDB 5.7.27 to 10.2Marko Mäkelä2019-07-251-1/+1
| |
* | Merge 10.1 into 10.2Marko Mäkelä2019-07-232-4/+4
|\ \ | |/
| * 5.6.44-86.0Marko Mäkelä2019-07-232-2/+2
| |
| * MDEV-20127 Merge new release of InnoDB 5.6.45 to 10.1Marko Mäkelä2019-07-233-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | There is one directly applicable change to InnoDB: commit 739f5239f12904247d2a61f9880ea1fafbedc332 in the 5.5 branch will be merged before the next MariaDB releases. Another potentially applicable change will be tracked separately as MDEV-20126. Thus, here we only update the InnoDB version number and do not change anything else.
* | MDEV-17228 Encrypted temporary tables are not encryptedThirunarayanan Balathandayuthapani2019-06-281-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | - Introduce a new variable called innodb_encrypt_temporary_tables which is a boolean variable. It decides whether to encrypt the temporary tablespace. - Encrypts the temporary tablespace based on full checksum format. - Introduced a new counter to track encrypted and decrypted temporary tablespace pages. - Warnings issued if temporary table creation has conflict value with innodb_encrypt_temporary_tables - Added a new test case which reads and writes the pages from/to temporary tablespace.
* | Merge 10.1 into 10.2Marko Mäkelä2019-05-134-4/+4
|\ \ | |/
| * Merge branch '5.5' into 10.1Vicențiu Ciorbaru2019-05-114-4/+4
| |\
* | \ Merge 10.1 into 10.2Jan Lindström2019-05-085-17/+12
|\ \ \ | |/ /
| * | MDEV-19387 innodb_ft_result_cache_limit_32 fails on s390xThirunarayanan Balathandayuthapani2019-05-085-17/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fix: ==== 1) Combined innodb_ft_result_cache_limit_32.test and innodb_ft_result_cache_limit_64.test test case in sys_vars suite. 2) Use word_size.inc for combinations of innodb_ft_result_cache_limit test case.
* | | Merge branch '10.1' into 10.2Oleksandr Byelkin2019-05-043-8/+9
|\ \ \ | |/ /
| * | MDEV-19331 Merge new release of InnoDB 5.6.44 to 10.1Marko Mäkelä2019-04-253-3/+3
| | |
| * | 5.6.43-84.3Marko Mäkelä2019-04-252-2/+2
| | |
| * | MDEV-19024 sys_vars.transaction_prealloc_size_bug27322 fails in buildbot ↵Sergei Golubchik2019-04-241-4/+5
| | | | | | | | | | | | | | | | | | | | | with wrong result Take into account ps-protocol states. Note, repace_regex was redundant, because Host column was replaced anyway
* | | MDEV-19342 Merge new release of InnoDB 5.7.26 to 10.2Marko Mäkelä2019-04-261-1/+1
| | |
* | | Merge branch '10.1' into 10.2Sergei Golubchik2019-03-152-1/+11
|\ \ \ | |/ /
| * | MDEV-15945 --ps-protocol does not test some queriesSergei Golubchik2019-03-122-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make mysqltest to use --ps-protocol more use prepared statements for everything that server supports with the exception of CALL (for now). Fix discovered test failures and bugs. tests: * PROCESSLIST shows Execute state, not Query * SHOW STATUS increments status variables more than in text protocol * multi-statements should be avoided (see tests with a wrong delimiter) * performance_schema events have different names in --ps-protocol * --enable_prepare_warnings mysqltest.cc: * make sure run_query_stmt() doesn't crash if there's no active connection (in wait_until_connected_again.inc) * prepare all statements that server supports protocol.h * Protocol_discard::send_result_set_metadata() should not send anything to the client. sql_acl.cc: * extract the functionality of getting the user for SHOW GRANTS from check_show_access(), so that mysql_test_show_grants() could generate the correct column names in the prepare step sql_class.cc: * result->prepare() can fail, don't ignore its return value * use correct number of decimals for EXPLAIN columns sql_parse.cc: * discard profiling for SHOW PROFILE. In text protocol it's done in prepare_schema_table(), but in --ps it is called on prepare only, so nothing was discarding profiling during execute. * move the permission checking code for SHOW CREATE VIEW to mysqld_show_create_get_fields(), so that it would be called during prepare step too. * only set sel_result when it was created here and needs to be destroyed in the same block. Avoid destroying lex->result. * use the correct number of tables in check_show_access(). Saying "as many as possible" doesn't work when first_not_own_table isn't set yet. sql_prepare.cc: * use correct user name for SHOW GRANTS columns * don't ignore verbose flag for SHOW SLAVE STATUS * support preparing REVOKE ALL and ROLLBACK TO SAVEPOINT * don't ignore errors from thd->prepare_explain_fields() * use select_send result for sending ANALYZE and EXPLAIN, but don't overwrite lex->result, because it might be needed to issue execute-time errors (select_dumpvar - too many rows) sql_show.cc: * check grants for SHOW CREATE VIEW here, not in mysql_execute_command sql_view.cc: * use the correct function to check privileges. Old code was doing check_access() for thd->security_ctx, which is invoker's sctx, not definer's sctx. Hide various view related errors from the invoker. sql_yacc.yy: * initialize lex->select_lex for LOAD, otherwise it'll contain garbage data that happen to fail tests with views in --ps (but not otherwise).
* | | Merge 10.1 into 10.2Marko Mäkelä2019-03-072-6/+6
|\ \ \ | |/ / | | | | | | | | | | | | Rewrite the MDEV-13818 fix to prevent heap-use-after-free. Add a test case for MDEV-18272.
| * | ASAN loves stack, give it someSergei Golubchik2019-03-065-15/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fixes these test failures in ASAN builds (in 10.1 and 10.4): * main.signal_demo3 * main.sp * sys_vars.max_sp_recursion_depth_func * mroonga/storage.foreign_key_delete_existent * mroonga/storage.foreign_key_delete_nonexistent * mroonga/storage.foreign_key_insert_existent * mroonga/storage.foreign_key_update_existent * mroonga/storage.foreign_key_update_nonexistent * mroonga/storage.function_command_auto-escape * mroonga/storage.function_command_select * mroonga/storage.variable_enable_operations_recording_insert
* | | cleanup: don't ---replace_regex /#sql-.*/#sql-temporary/Sergei Golubchik2019-02-052-2/+1
| | | | | | | | | | | | no longer needed
* | | Merge 10.1 into 10.2Marko Mäkelä2019-02-032-4/+4
|\ \ \ | |/ / | | | | | | | | | | | | Temporarily disable a test for commit 2175bfce3e9da8332f10ab0e0286dc93915533a2 because fixing it in 10.2 requires updating libmariadb.
View Lorry Controller Status