An error occurred fetching the project authors.
- 24 May, 2010 1 commit
-
-
Some of the test cases reference to binlog position and these position numbers are written into result explicitly. It is difficult to maintain if log event format changes. There are a couple of cases explicit position number appears, we handle them in different ways A. 'CHANGE MASTER ...' with MASTER_LOG_POS or/and RELAY_LOG_POS options Use --replace_result to mask them. B. 'SHOW BINLOG EVENT ...' Replaced by show_binlog_events.inc or wait_for_binlog_event.inc. show_binlog_events.inc file's function is enhanced by given $binlog_file and $binlog_limit. C. 'SHOW SLAVE STATUS', 'show_slave_status.inc' and 'show_slave_status2.inc' For the test cases just care a few items in the result of 'SHOW SLAVE STATUS', only the items related to each test case are showed. 'show_slave_status.inc' is rebuild, only the given items in $status_items will be showed. 'check_slave_is_running.inc' and 'check_slave_no_error.inc' and 'check_slave_param.inc' are auxiliary files helping to show running status and error information easily.
-
- 16 Jul, 2008 1 commit
-
-
Sven Sandberg authored
Post-post-push fix. The result file for rpl_rbr_to_sbr needs to be updated. While I was there, made rpl_rbr_to_sbr clean up after itself by reverting @@binlog_format to the value it had before the test started.
-
- 27 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Update mysql-test-run.pl to collect tests from several suites - Group test into suites - Add suite.opt file
-
- 09 Jun, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
Adding new fields Last_{IO,SQL}_Errno and Last_{IO,SQL}_Error to output of SHOW SLAVE STATUS to hold errors from I/O and SQL thread respectively. Old fields Last_Error and Last_Errno are aliases for Last_SQL_Error and Last_SQL_Errno respectively. Fields are added last to output of SHOW SLAVE STATUS to allow old applications to use the same positional arguments into the row, while allowing new application to benefit from the added information. In addition, some new error codes are added (especially for the I/O thread) to be able to provide sensible error message.
-
- 16 Apr, 2007 1 commit
-
-
monty@mysql.com/narttu.mysql.fi authored
Change to use remove_file instead of 'system rm' in a lot of tests. (Should fix some windows test problems) Removed memory leak in mysql_test if sync_with_master fails. Do not terminate ndb_cluster_binary_log before the util thread has finnished. This should fix a shutdown bug where a thread is accessing injector_mutex after it's freed. Patch may fix Bug#27622 "mysqld shutdown, util thread continues, while binlog thread exits"
-
- 20 Feb, 2007 1 commit
-
-
msvensson@pilot.blaudden authored
-
- 07 Dec, 2006 1 commit
-
-
cbell/Chuck@suse.vabb.com authored
Please see worklog for details on files changed.
-
- 15 Sep, 2006 1 commit
-
-
A query SET @@GLOBAL.binlog_format = ... returns an error when NDB is the default storage. This fails some tests invoking the set binlog_format explicitly. because the var turns to be read-only. In the following are files and method to fix if needed. t/ ndb_binlog_basic2.test # here the failure is benign rpl_rbr_to_sbr.test # does not check any ndb features => . # => not_ndb_default is enough rpl_row_basic_8partition.test # set binlog_format can be replaced rpl_switch_stm_row_mixed.test # does not check any ndb features => . # => not_ndb_default is enough two more invoking invoke extra/rpl_truncate_helper.test rpl_truncate_2myisam # to be fixed with not_ndb_default rpl_truncate_3innodb # same as above . # because there is a dedicated to ndb . . # rpl_truncate_7ndb* suit. Adapting/testing a new implement --source include/safe_set_to_maybe_ro_var.inc to avoid abort due to the error using binlog_format as application.
-
- 30 Aug, 2006 1 commit
-
-
aelkin/elkin@andrepl.dsl.inet.fi authored
The following is an excerption from the WL. 1. Change so that MIXED is default format 1.1 to change the default for command line --binlog-format 1.2 to alter global_system_variables.binlog_format calculation basing on command line --binlog-format parameter and its default. 2. Change test suite so that more testing is done by MIXED format. 2.1 to check if there are test cases requiring --binlog-foramt=statement via `source include/have_binlog_format_statement.inc' and affected by altering the latter to be "mixed". 2.2 to check the content of such vulnerable cases to find if extending to the mixed does not modify results. In that case simply substitute source arguments as explained. 2.3 if a test in mixed mode deals with features triggering row-binlogging then if necessary we can switch explicitly to statement mode or create another test to run with non-recommended STATEMENT mode Particullarily, extracting INSERT DELAYED binlogging subtest for statement mode is performed, and the snippet is moved into a separate test file. Note that since now all three modes verify this use case through 3 different tests. No changes in item 3 of HLD appeared to be needed.
-
- 16 May, 2006 1 commit
-
-
mats@mysql.com authored
Added #ifdef's to make code work even when the system is built without row-based replication.
-
- 14 Mar, 2006 1 commit
-
-
gbichot@production.mysql.com authored
(nothing to document, this bug was not released).
-
- 08 Mar, 2006 1 commit
-
-
mats@mysql.com authored
Removed error on seeing table map event when slave is in SBR mode and switching temporarily to RBR mode to replicate the rows.
-