mariadb/mysql-test/suite/perfschema/t/rollback_table_io.test
Sergei Golubchik 474fe6d9d9 fixes for test failures
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
2012-09-27 20:09:46 +02:00

48 lines
1.2 KiB
Text

# Tests for PERFORMANCE_SCHEMA table io
# Show the impact of a rollback in case of the transactional engine InnoDB
# Setup
--source include/not_embedded.inc
--source include/have_perfschema.inc
--source include/have_innodb.inc
--disable_warnings
drop table if exists test.t1;
--enable_warnings
let $engine_type= InnoDB;
eval create table test.t1 (col1 bigint, col2 varchar(30)) engine = $engine_type;
show create table test.t1;
insert into test.t1 values(1,'One');
eval set default_storage_engine=$engine_type;
--source ../include/table_io_setup_helper.inc
let $schema_to_dump= 'test';
# Start recording of events
update performance_schema.setup_consumers set enabled = 'YES';
set autocommit = off;
# Code to test
delete from test.t1 where col1 = 1;
insert into marker set a = 1;
rollback;
insert into marker set a = 1;
update test.t1 set col2 = 'Updated' where col1 = 1;
insert into marker set a = 1;
rollback;
insert into marker set a = 1;
insert into test.t1 values(2,'Two');
insert into marker set a = 1;
rollback;
# Stop recording of events + pull results
--source ../include/table_io_result_helper.inc
# Cleanup
drop table test.t1;
--source ../include/table_io_cleanup_helper.inc