mirror of
https://github.com/MariaDB/server.git
synced 2025-11-21 06:21:35 +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
44 lines
1.4 KiB
PHP
44 lines
1.4 KiB
PHP
# ==== Purpose ====
|
|
#
|
|
# Execute SHOW BINLOG EVENTS and mask non-deterministic output.
|
|
#
|
|
# ==== Usage ====
|
|
#
|
|
# [--let $binlog_file= [<FILENAME> | LAST]]
|
|
# [--let $binlog_start= <POSITION> ]
|
|
# [--let $binlog_limit= 1, 3 ]
|
|
# [--let $keep_gtid_events= 1]
|
|
# --source include/show_binlog_events.inc
|
|
#
|
|
# Parameters:
|
|
#
|
|
# $binlog_file
|
|
# Filename for the 'IN' clause of SHOW BINLOG EVENTS. If none
|
|
# given, no argument is given to SHOW BINLOG EVENTS, meaning that
|
|
# it uses the first binlog. If you set this to "LAST", it prints
|
|
# the last binlog (according to SHOW MASTER STATUS).
|
|
#
|
|
# $binlog_start
|
|
# Position for the 'FROM' clause of SHOW BINLOG EVENTS. If none
|
|
# given, starts right after the Format_description_log_event.
|
|
#
|
|
# $binlog_limit
|
|
# Limit for the 'LIMIT' clause of SHOW BINLOG EVENTS, i.e.:
|
|
# $binlog_limit= 3 -- print three events
|
|
# $binlog_limit= 4, 3 -- skip four events, print the three next events
|
|
#
|
|
# $keep_gtid_events
|
|
# By default, Gtid_log_event and Previous_gtid_log_event are
|
|
# filtered out, so that the output is independent of whether GTIDs
|
|
# are enabled or not. If this flag is set, events are kept but
|
|
# the actual GTID values are masked out.
|
|
|
|
--let $include_filename= show_binlog_events.inc
|
|
--source include/begin_include_file.inc
|
|
|
|
--let $is_relay_log= 0
|
|
--source include/show_events.inc
|
|
|
|
--let $include_filename= show_binlog_events.inc
|
|
--source include/end_include_file.inc
|