1. 24 Feb, 2007 7 commits
  2. 23 Feb, 2007 5 commits
    • gbichot@dl145h.mysql.com's avatar
      Fix for BUG#25628: "mysqlbinlog crashes while processing binary logs". · ba2452f0
      gbichot@dl145h.mysql.com authored
      mysqlbinlog prints all row-based events of a single statement as a
      single "BINLOG" statement containing the concatenation of those events.
      Big (i.e. >64k) concatenations of row-based events
      (e.g. Write_rows_log_event) caused mysqlbinlog's IO_CACHE to overflow
      to a temporary file but the IO_CACHE had not been inited with
      open_cached_file(), so it tried to create a temporary file in
      an uninitialized directory (thus failing to create, then to write;
      some OS errors were printed, and it finally segfaulted).
      After fixing this, it appeared that mysqlbinlog was printing only
      a piece of big concatenations of row-based events (it printed
      at most the size of the IO_CACHE's buffer i.e. 64k); that caused data
      loss at restore. We fix and test that.
      Last, mysqlbinlog's printouts looked a bit strange with the informative
      header (#-prefixed) of groupped Rows_log_event all on one line,
      so we insert \n. After that, a small bug in the --hexdump code appeared
      (only if the string to hex-print had its length a multiple of 16),
      we fix it.
      ba2452f0
    • gbichot@dl145h.mysql.com's avatar
      Merge dl145h.mysql.com:/users/gbichot/mysql-5.0-rpl · 84f875cf
      gbichot@dl145h.mysql.com authored
      into  dl145h.mysql.com:/users/gbichot/mysql-5.1-rpl
      84f875cf
    • mats@romeo.(none)'s avatar
      BUG#19033 (RBR: slave does not handle schema changes correctly): · 54b04ff5
      mats@romeo.(none) authored
      Post-merge fixes.
      54b04ff5
    • gbichot@dl145h.mysql.com's avatar
      the fix for BUG#24432 · 44c6c4cc
      gbichot@dl145h.mysql.com authored
        "INSERT... ON DUPLICATE KEY UPDATE skips auto_increment values"
      didn't make it into 5.0.36 and 5.1.16,
      so we need to adjust the bug-detection-based-on-version-number code.
      Because the rpl tree has a too old version, rpl_insert_id cannot pass,
      so I disable it (like is already the case in 5.1-rpl for the same reason),
      and the repl team will re-enable it when they merge 5.0 and 5.1 into
      their trees (thus getting the right version number).
      44c6c4cc
    • mats@romeo.(none)'s avatar
      Merge romeo.(none):/home/bkroot/mysql-5.1-new-rpl · 2114ea31
      mats@romeo.(none) authored
      into  romeo.(none):/home/bk/b19033-mysql-5.1-new-rpl
      2114ea31
  3. 21 Feb, 2007 11 commits
  4. 20 Feb, 2007 13 commits
  5. 19 Feb, 2007 4 commits