An error occurred fetching the project authors.
  1. 24 May, 2010 1 commit
    • 's avatar
      Bug #49741 test files contain explicit references to bin/relay-log positions · cc054408
      authored
      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.
      cc054408
  2. 16 Jul, 2008 1 commit
  3. 27 Jun, 2007 1 commit
  4. 09 Jun, 2007 1 commit
    • mats@kindahl-laptop.dnsalias.net's avatar
      BUG#24954 (Last_errno and Last_error not set after master_retry_count was reached): · 9094e97a
      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.
      9094e97a
  5. 16 Apr, 2007 1 commit
  6. 20 Feb, 2007 1 commit
  7. 07 Dec, 2006 1 commit
  8. 15 Sep, 2006 1 commit
    • aelkin/elkin@dsl-hkigw8-fe00f800-98.dhcp.inet.fi's avatar
      Bug#22067 rpl_rbr_to_sbr and some other fail if NDB is default storage · 6055e8a9
      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.
      6055e8a9
  9. 30 Aug, 2006 1 commit
    • aelkin/elkin@andrepl.dsl.inet.fi's avatar
      Changes made according to HLD/LLD. · 7be4bc4e
      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.
      7be4bc4e
  10. 16 May, 2006 1 commit
  11. 14 Mar, 2006 1 commit
  12. 08 Mar, 2006 1 commit