An error occurred fetching the project authors.
  1. 17 Aug, 2010 1 commit
    • Sergei Golubchik's avatar
      generalization of mtr to support suite.pm extensions: · 8da7be63
      Sergei Golubchik authored
      * no automatic --loose-skip-innodb added by mtr based on the test name.
        instead loose-skip-innodb is now in the default_mysqld.cnf
      * have_innodb_plugin.inc is changed to give a verbose "skip" message
        (instead of "require: true")
      * My::Suite class. It's support in mtr, and everywhere
      * support for suite.pm
      * when sorting tests, take combinations into account
      * support for SUITENAME_COMBINATIONS
      * no special treatment for innodb_plugin in mtr_cases.pm
      * two special pre-created config groups: ENV and OPT
      * allow option names to start from #
      * allow magic option to have an argument
      * remove dead code
      * fix @-substitution to works as expected
      * new processes take the value of $opt_verbose automatically, no need to pass it to a constructor
      * innodb_plugin suite uses suite.pm and combinations file to test as much as possible
        (innodb plugin, xtradb plugin, xtradb static - whatever available)
      * besides test-master.opt and test-slave.opt a test.opt file is also
        loaded, both for master and slave
      * .opt files for all included files are loaded too
      * progress report in the xterm titlebar
      8da7be63
  2. 26 Mar, 2009 1 commit
    • Andrei Elkin's avatar
      Bug#38205 Row-based Replication (RBR) causes inconsistencies: HA_ERR_FOUND_DUP · 21cc7d5a
      Andrei Elkin authored
      Bug#319  if while a non-transactional slave is replicating a transaction possible problem 
      
      It is impossible to roll back a mixed engines transaction when one of the engine is
      non-transaction. In replication that fact is crucial because the slave can not safely
      re-apply a transction that was interrupted with STOP SLAVE.
      
      Fixed with making STOP SLAVE not be effective immediately in the case the current
      group of replication events has modified a non-transaction table. In order for slave to leave
      either the group needs finishing or the user issues KILL QUERY|CONNECTION slave_thread_id.
      
      
      mysql-test/suite/bugs/r/rpl_bug38205.result:
        bug#38205 non-deterministic part of tests results.
      mysql-test/suite/bugs/t/rpl_bug38205.test:
        bug#38205 non-deterministic part of tests.
      mysql-test/suite/rpl/r/rpl_start_stop_slave.result:
        bug#38205 deterministic part of tests results.
      mysql-test/suite/rpl/t/rpl_start_stop_slave-slave.opt:
        increasing `innodb_lock_wait_timeout' to make the test pass on slow env w/o
        timeout expired issue.
      mysql-test/suite/rpl/t/rpl_start_stop_slave.test:
        bug#38205 deterministic part of tests.
      sql/log_event.cc:
        Augmenting row-based events applying with the notion of 
        thd->transaction.{all,stmt}.modified_non_trans_table.
        The pair is set and reset according to its specification
        for the mixed transaction processing.
        Particualry, once `modified_non_trans_table' is set in the row-events
        processing loop, it will remain till the commit of the transaction.
      sql/slave.cc:
        Consulting `thd->transaction.all.modified_non_trans_table' to decide
        whether to terminate by the sql thread or to continue even though
        the sql thread might have been STOP-ed (rli->abort_slave).
      21cc7d5a