An error occurred fetching the project authors.
- 17 Nov, 2010 1 commit
-
-
Bjorn Munch authored
-
- 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.
-
- 27 Nov, 2009 1 commit
-
-
Serge Kozlov authored
-
- 02 Oct, 2009 1 commit
-
-
He Zhenxing authored
CHANGE MASTER TO command required the value for RELAY_LOG_FILE to be an absolute path, which was different from the requirement of MASTER_LOG_FILE. This patch fixed the problem by changing the value for RELAY_LOG_FILE to be the basename of the log file as that for MASTER_LOG_FILE.
-
- 28 Feb, 2008 1 commit
-
-
skozlov/ksm@mysql.com/virtop.(none) authored
-
- 14 Jan, 2008 1 commit
-
-
hezx@mail.hezx.com authored
Mask binlog positions, error, warning and other information that are not significant for the test
-
- 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
-
- 19 Jun, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
counters from relay Updated the test to return columns vertically.
-
- 11 Jun, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
been reached): Post-merge patch to handle all the changes to the tree since the tree was cloned.
-
- 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.
-
- 19 Oct, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-
- 22 Dec, 2005 1 commit
-
-
lars@mysql.com authored
This includes both code and test cases.
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 15 Jul, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Fixed problem, only detect comment if the # is on start of line AND starting line of the current command. - Wrote tests for most of the mysqltest commands, added stricter checking of correct syntax.
-
- 02 Mar, 2005 1 commit
-
-
guilhem@mysql.com authored
Last part of fix for BUG#7998 "Replication should be more clever about when to replicate RELEASE_LOCK()" + fixes after merge
-
- 19 Dec, 2003 1 commit
-
-
guilhem@gbichot2 authored
* A more dynamic binlog format which allows small changes (1064) * Log session variables in Query_log_event (1063) It contains a few bugfixes (which I made when running the testsuite). I carefully updated the results of the testsuite (i.e. I checked for every one, if the difference between .reject and .result could be explained). Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently, so I could neither run the few tests which require --manager, nor check that they pass nor modify their .result. But for builds, we don't run with --manager. Apart from --manager, the full testsuite passes, with Valgrind too (no errors). I'm going to push in the next minutes. Remains: update the manual. Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone; this is normal at it makes assumptions on thread ids. I will fix this one day in 4.1.
-
- 25 Nov, 2003 1 commit
-
-
monty@mysql.com authored
-
- 23 Nov, 2003 1 commit
-
-
monty@mysql.com authored
-
- 22 Nov, 2003 1 commit
-
-
monty@mysql.com authored
Don't flush cur_log (relay log) on flush_relay_log_info becasue this crashes the server if cur_log is 'hot' and the io_thread has changed log file. Updated project files for windows Made rpl_change_master.test portable Ensure that mutex are not freed if not initilized
-
- 20 Nov, 2003 1 commit
-
-
monty@mysql.com authored
Portability fixes After merge fixes
-
- 18 Nov, 2003 1 commit
-
-
guilhem@mysql.com authored
"CHANGE MASTER makes SQL thread restart from coordinates of I/O thread". So, in CHANGE MASTER: when it seems reasonable that the user did not want to discontinue its replication (i.e. when he is not specifying host or port or master_log_file or master_log_pos; this will be documented), set the coordinates of the I/O thread to those of the SQL thread. This way, the SQL thread will see no discontinuity in the relay log (i.e. will skip no events), because the I/O thread will fill the brand new relay log with the events which are just after the position where the SQL thread had stopped (before CHANGE MASTER was issued). And a new test for this bug.
-