mirror of
https://github.com/MariaDB/server.git
synced 2025-10-25 18:38:00 +03:00
474fe6d9d9
and small collateral changes mysql-test/lib/My/Test.pm: somehow with "print" we get truncated writes sometimes mysql-test/suite/perfschema/r/digest_table_full.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/perfschema/r/dml_handler.result: host table is not ported over yet mysql-test/suite/perfschema/r/information_schema.result: host table is not ported over yet mysql-test/suite/perfschema/r/nesting.result: this differs, because we don't rewrite general log queries, and multi-statement packets are logged as a one entry. this result file is identical to what mysql-5.6.5 produces with the --log-raw option. mysql-test/suite/perfschema/r/relaylog.result: MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB. mysql-test/suite/perfschema/r/server_init.result: MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup. mysql-test/suite/perfschema/r/stage_mdl_global.result: this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not do that, and this causes useless mutex locks and waits. mysql-test/suite/perfschema/r/statement_digest.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/perfschema/r/statement_digest_consumers.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/perfschema/r/statement_digest_long_query.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result: will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result: will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
69 lines
1.7 KiB
Plaintext
69 lines
1.7 KiB
Plaintext
SELECT @@GLOBAL.innodb_undo_logs;
|
|
@@GLOBAL.innodb_undo_logs
|
|
128
|
|
128 Expected
|
|
SET @@GLOBAL.innodb_undo_logs=128;
|
|
SELECT COUNT(@@GLOBAL.innodb_undo_logs);
|
|
COUNT(@@GLOBAL.innodb_undo_logs)
|
|
1
|
|
1 Expected
|
|
SELECT VARIABLE_VALUE
|
|
FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES
|
|
WHERE VARIABLE_NAME='innodb_undo_logs';
|
|
VARIABLE_VALUE
|
|
128
|
|
128 Expected
|
|
SELECT @@innodb_undo_logs = @@GLOBAL.innodb_undo_logs;
|
|
@@innodb_undo_logs = @@GLOBAL.innodb_undo_logs
|
|
1
|
|
1 Expected
|
|
SELECT COUNT(@@innodb_undo_logs);
|
|
COUNT(@@innodb_undo_logs)
|
|
1
|
|
1 Expected
|
|
SELECT COUNT(@@local.innodb_undo_logs);
|
|
ERROR HY000: Variable 'innodb_undo_logs' is a GLOBAL variable
|
|
Expected error 'Variable is a GLOBAL variable'
|
|
SELECT COUNT(@@SESSION.innodb_undo_logs);
|
|
ERROR HY000: Variable 'innodb_undo_logs' is a GLOBAL variable
|
|
Expected error 'Variable is a GLOBAL variable'
|
|
SELECT innodb_undo_logs = @@SESSION.innodb_undo_logs;
|
|
ERROR 42S22: Unknown column 'innodb_undo_logs' in 'field list'
|
|
Begin bug 13604034
|
|
select @@innodb_undo_logs;
|
|
@@innodb_undo_logs
|
|
128
|
|
128 Expected
|
|
set global innodb_undo_logs = 129;
|
|
Warnings:
|
|
Warning 1292 Truncated incorrect innodb_undo_logs value: '129'
|
|
select @@innodb_undo_logs;
|
|
@@innodb_undo_logs
|
|
128
|
|
128 Expected
|
|
set global innodb_undo_logs = 0;
|
|
Warnings:
|
|
Warning 1292 Truncated incorrect innodb_undo_logs value: '0'
|
|
select @@innodb_undo_logs;
|
|
@@innodb_undo_logs
|
|
1
|
|
1 Expected
|
|
set global innodb_undo_logs = -1;
|
|
Warnings:
|
|
Warning 1292 Truncated incorrect innodb_undo_logs value: '-1'
|
|
select @@innodb_undo_logs;
|
|
@@innodb_undo_logs
|
|
1
|
|
1 Expected
|
|
set global innodb_undo_logs = 50;
|
|
select @@innodb_undo_logs;
|
|
@@innodb_undo_logs
|
|
50
|
|
50 Expected
|
|
set global innodb_undo_logs = default;
|
|
select @@innodb_undo_logs;
|
|
@@innodb_undo_logs
|
|
128
|
|
128 Expected
|
|
End bug 13604034
|