1. 06 Jan, 2008 1 commit
  2. 02 Jan, 2008 1 commit
  3. 24 Dec, 2007 1 commit
  4. 23 Dec, 2007 1 commit
  5. 22 Dec, 2007 1 commit
  6. 21 Dec, 2007 8 commits
  7. 20 Dec, 2007 1 commit
    • mats@capulet.kindahl.net's avatar
      BUG#12691 (Exec_master_log_pos corrupted with SQL_SLAVE_SKIP_COUNTER): · f1c32705
      mats@capulet.kindahl.net authored
      Complementary patch since LOAD DATA INFILE was not covered in
      the previous patch.
      
      This patch adds a check so that the slave skip counter is not
      decreased to zero if seeing a BEGIN_LOAD_QUERY_EVENT,
      APPEND_BLOCK_EVENT, or CREATE_FILE_EVENT since these cannot
      end a group. The group is terminated by an EXECUTE_LOAD_QUERY_
      EVENT or DELETE_FILE_EVENT.
      f1c32705
  8. 18 Dec, 2007 1 commit
  9. 15 Dec, 2007 1 commit
    • hezx@hezx.(none)'s avatar
      BUG#32205 Replaying statements from mysqlbinlog fails with a syntax error, replicates fine · c2f00cc3
      hezx@hezx.(none) authored
      The reason of this bug is that when mysqlbinlog dumps a query, the query is written to
      output with a delimeter appended right after it, if the query string ends with a '--'
      comment, then the delimeter would be considered as part of the comment, if there are any
      statements after this query, then it will cause a syntax error.
      
      Start a newline before appending delimiter after a query string
      c2f00cc3
  10. 11 Dec, 2007 1 commit
  11. 05 Dec, 2007 1 commit
  12. 03 Dec, 2007 1 commit
    • hezx@hezx.(none)'s avatar
      Bug#30998 Drop View breaks replication if view does not exist · c267a923
      hezx@hezx.(none) authored
        
      When executing drop view statement on the master, the statement is written
      into bin-log without checking for possible errors, so the statement would 
      always be bin-logged with error code cleared even if some error might occur, 
      for example, some of the views being dropped does not exist. This would cause 
      failure on the slave.
      
      Writing bin-log after check for errors, if at least one view has been dropped
      the query is bin-logged possible with an error.
      c267a923
  13. 22 Nov, 2007 1 commit
  14. 14 Nov, 2007 3 commits
  15. 13 Nov, 2007 2 commits
  16. 12 Nov, 2007 1 commit
  17. 10 Nov, 2007 1 commit
  18. 09 Nov, 2007 3 commits
    • mats@capulet.net's avatar
      Merge capulet.net:/home/bk/mysql-5.0-rpl · a88babcb
      mats@capulet.net authored
      into  capulet.net:/home/mats/devel/b31793-mysql-5.0-rpl
      a88babcb
    • mats@capulet.net's avatar
      Merge mkindahl@bk-internal.mysql.com:/home/bk/mysql-5.0-rpl · d5ccec26
      mats@capulet.net authored
      into  capulet.net:/home/bk/mysql-5.0-rpl
      d5ccec26
    • mats@capulet.net's avatar
      BUG#31793 (log event corruption causes crash): · a432d3de
      mats@capulet.net authored
      When running mysqlbinlog on a 64-bit machine with a corrupt relay log,
      it causes mysqlbinlog to crash. In this case, the crash is caused
      because a request for 18446744073709534806U bytes is issued, which
      apparantly can be served on a 64-bit machine (speculatively, I assume)
      but this causes the memcpy() issued later to copy the data to segfault.
      
      The request for the number of bytes is caused by a computation
      of data_len - server_vars_len where server_vars_len is corrupt in such
      a sense that it is > data_len. This causes a wrap-around, with the
      the data_len given above.
      
      This patch adds a check that if server_vars_len is greater than
      data_len before the substraction, and aborts reading the event in
      that case marking the event as invalid. It also adds checks to see
      that reading the server variables does not go outside the bounds
      of the available space, giving a limited amount of integrity check.
      a432d3de
  19. 06 Nov, 2007 7 commits
  20. 05 Nov, 2007 3 commits
    • malff@lambda.hsd1.co.comcast.net.'s avatar
      Merge lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.0-base · 00f1af47
      malff@lambda.hsd1.co.comcast.net. authored
      into  lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.0-rt-merge
      00f1af47
    • aelkin/elkin@koti.dsl.inet.fi's avatar
      Merge aelkin@bk-internal.mysql.com:/home/bk/mysql-5.0-rpl · 27636d56
      aelkin/elkin@koti.dsl.inet.fi authored
      into  koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug28597-log_name_upgrade
      27636d56
    • aelkin/elkin@koti.dsl.inet.fi's avatar
      Bug #28597 Replication doesn't start after upgrading to 5.1.18 · 571f8be4
      aelkin/elkin@koti.dsl.inet.fi authored
      Since bug@20166, which replaced the binlog file name generating to base
      on pidfile_name instead of the previous glob_hostname, the binlog file
      name suddenly started to be stored solely in the absolute path format,
      including a case when --log-bin option meant a relative path.
      What's more serious, the path for binlog file can lead unrequestedly 
      to pid-file directory so that after any proper fix for this bug
      there might be similar to the bug report consequences for one who
      upgrades from post-fix-bug@20166-pre-fix-bug@28597 to post-fix-bug@28597.
      
      Fixed with preserving`pidfile_name' (intr.by bug@20166) but stripping
      off its directory part. This restores the original logics of storing
      the names in compatible with --log-bin option format and with the
      requirement for --log-bin ralative path to corresond to the data directory.
      Side effects for this fix:
      
      effective fixing bug@27070, refining its test;
      ensuring no overrun for buff can happen anymore (Bug#31836 
      insufficient space reserved for the suffix of relay log file name);
      bug#31837  --remove_file $MYSQLTEST_VARDIR/tmp/bug14157.sql missed
      in rpl_temporary.test;
      fixes Bug@28603  Invalid log-bin default location;
      571f8be4