An error occurred fetching the project authors.
  1. 10 Feb, 2009 1 commit
  2. 06 Feb, 2009 1 commit
    • Mats Kindahl's avatar
      Bug #36763 · e3708c23
      Mats Kindahl authored
      TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported.
      
      There were two separate problems with the code, both of which are fixed with
      this patch:
      
      1. An error was printed by InnoDB for TRUNCATE TABLE in statement mode when
         the in isolation levels READ COMMITTED and READ UNCOMMITTED since InnoDB
         does permit statement-based replication for DML statements. However,
         the TRUNCATE TABLE is not transactional, but is a DDL, and should therefore
         be allowed to be replicated as a statement.
      
      2. The statement was not logged in mixed mode because of the error above, but
         the error was not reported to the client.
      
      This patch fixes the problem by treating TRUNCATE TABLE a DDL, that is, it is
      always logged as a statement and not reporting an error from InnoDB for TRUNCATE
      TABLE.
      e3708c23
  3. 13 Nov, 2008 1 commit
    • Sven Sandberg's avatar
      BUG#38350: Many tests don't clean up after themselves on exit. · 78a3abec
      Sven Sandberg authored
      Problem: Many test cases don't clean up after themselves (fail
      to drop tables or fail to reset variables). This implies that:
      (1) check-testcase in the new mtr that currently lives in
      5.1-rpl failed. (2) it may cause unexpected results in
      subsequent tests.
      Fix: make all tests clean up.
      Also: cleaned away unnecessary output in rpl_packet.result
      Also: fixed bug where rpl_log called RESET MASTER with a running
      slave. This is not supposed to work.
      Also: removed unnecessary code from rpl_stm_EE_err2 and made it
      verify that an error occurred.
      Also: removed unnecessary code from rpl_ndb_ctype_ucs2_def.
      78a3abec
  4. 28 Mar, 2008 1 commit
    • mats@mats-laptop.(none)'s avatar
      BUG#29020 (Event results not correctly replicated to slave in RBR): · c8c4500a
      mats@mats-laptop.(none) authored
      The bug allow multiple executing transactions working with non-transactional
      to interfere with each others by interleaving the events of different trans-
      actions.
      
      Bug is fixed by writing non-transactional events to the transaction cache and
      flushing the cache to the binary log at statement commit. To mimic the behavior
      of normal statement-based replication, we flush the transaction cache in row-
      based mode when there is no committed statements in the transaction cache,
      which means we are committing the first one. This means that it will be written
      to the binary log as a "mini-transaction" with just the rows for the statement.
      
      Note that the changes here does not take effect when building the server with
      HAVE_TRANSACTIONS set to false, but it is not clear if this was possible before
      this patch either.
      
      For row-based logging, we also have that when AUTOCOMMIT=1, the code now always
      generates a BEGIN/COMMIT pair for single statements, or BEGIN/ROLLBACK pair in the
      case of non-transactional changes in a statement that was rolled back. Note that
      for the case where changes to a non-transactional table causes a rollback due
      to error, the statement will now be logged with a BEGIN/ROLLBACK pair, even
      though some changes has been committed to the non-transactional table.
      c8c4500a
  5. 02 Nov, 2007 1 commit
    • aelkin/elkin@koti.dsl.inet.fi's avatar
      Bug #31554 rpl.rpl_truncate_2myisam test failure: wrong master binlog file name · 4b9b0154
      aelkin/elkin@koti.dsl.inet.fi authored
      Actually, the failure happened with 3innodb as well. Most probably
      the reason is in failing to delete a binlog file on __NT__ so that
      that master increments the index of the binlog file.
      The test results hide valueable warning that windows could generate
      about that.
      
      The scope of this fix is to make sure we have such warning and
      to lessen chances for binlog file being held at time of closing.
      The dump thread is getting a good chance to leave and 
      release the file for its successful deletion.
      
      We shall watch over the two tests as regression is not excluded.
      In that case we would have an extra info possibly explaining why
      __NT__ env can not close/delete the file.
      However, regardless of that reason, there is alwasy workaround to mask out
      non-deterministic binlog index number.
      4b9b0154
  6. 27 Jun, 2007 1 commit
  7. 30 Mar, 2007 2 commits
  8. 29 Mar, 2007 1 commit
    • mats@romeo.(none)'s avatar
      WL#3464: Add replication event to denote gap in replication · 7c187c2c
      mats@romeo.(none) authored
      Adding an event that can be used to denote that an incident occured
      on the master. The event can be used to denote a gap in the replication
      stream, but can also be used to denote other incidents.
      
      In addition, the injector interface is extended with functions to
      generate an incident event. The function will also rotate the binary
      log after generating an incident event to get a fresh binary log.
      7c187c2c
  9. 12 Feb, 2007 1 commit
  10. 13 Jun, 2006 1 commit
  11. 01 Jun, 2006 1 commit