1. 26 Jul, 2003 2 commits
  2. 25 Jul, 2003 3 commits
    • unknown's avatar
      srv0srv.c, os0file.c, log0recv.h, log0log.h, fil0fil.h, fsp0fsp.c, fil0fil.c: · d9472d2f
      unknown authored
        Merge
      trx0trx.c:
        Print more info about a trx in SHOW INNODB status; try to find the bug reported by Plaxo
      buf0buf.c:
        Check that page log sequence numbers are not in the future
      log0recv.c, log0log.c:
        Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
      
      
      innobase/log/log0log.c:
        Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
      innobase/log/log0recv.c:
        Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
      innobase/buf/buf0buf.c:
        Check that page log sequence numbers are not in the future
      innobase/trx/trx0trx.c:
        Print more info about a trx in SHOW INNODB status; try to find the bug reported by Plaxo
      innobase/fil/fil0fil.c:
        Merge
      innobase/fsp/fsp0fsp.c:
        Merge
      innobase/include/fil0fil.h:
        Merge
      innobase/include/log0log.h:
        Merge
      innobase/include/log0recv.h:
        Merge
      innobase/os/os0file.c:
        Merge
      innobase/srv/srv0srv.c:
        Merge
      d9472d2f
    • unknown's avatar
      Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-4.0 · 35105021
      unknown authored
      into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.fix
      
      35105021
    • unknown's avatar
      Fix: remove compile warnings on RH(with openssl) · bdf8908e
      unknown authored
      bdf8908e
  3. 24 Jul, 2003 4 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · ba375ff0
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      ba375ff0
    • unknown's avatar
      Fix for BUG#858 "CHANGE MASTER forgets to update relay-log.info"; · d1fc0bae
      unknown authored
      just a flush_relay_log_info() at the end of CHANGE MASTER
      (there was already flush_master_info()).
      
      
      sql/sql_repl.cc:
        Comments.
        Flush relay-log.info after CHANGE MASTER, or the changes
        to the relay log parameters (relay log name and position, and
        the corresponding master's binlog name and position) will be
        lost if the slave mysqld is shutdown immediately after the 
        CHANGE MASTER (without the slave threads being started).
      d1fc0bae
    • unknown's avatar
      WL#1036 (print the db in slave error messages). · adedde52
      unknown authored
      I extended the task to cleaning error messages, making them look nicer,
      and making the output of SHOW SLAVE STATUS (column Last_error) be as complete
      as what's printed on the .err file;
      previously we would have, for a failure of a replicated LOAD DATA INFILE:
      - in the .err, 2 lines:
      "duplicate entry 2708 for key 1"
      "failed loading SQL_LOAD-5-2-2.info"
      - and in SHOW SLAVE STATUS, only:
      "failed loading SQL_LOAD-5-2-2.info".
      Now SHOW SLAVE STATUS will contain the concatenation of the 2 messages.
      
      
      sql/log_event.cc:
        Print the default database when replication stops because of an error. Previously, we had:
        "error "Duplicate entry 87987 for key 1", query 'insert into t values(87987)'", ie the db
        was not mentioned, making it hard for cases where the same table name is used in
        several databases.
        Lengthened some error messages (for failing replication of LOAD DATA: mention the table
        and the db).
        Changes so that SHOW SLAVE STATUS reports as complete errors as the .err file.
      sql/slave.cc:
        Removed a useless declaration (the rewrite_db() function is already declared in slave.h).
        Added missing ')' in error messages.
        Tried to make error messages look nicer (previously we had
        "do START SLAVE;, error_code=1062"
        now we'll have
        "do START SLAVE; . Error_code=1062".
        This form has been discussed, I agree it's no panacea, but it's still more readable
        like this. To be improved in the future :)
      sql/slave.h:
        declarations.
      adedde52
    • unknown's avatar
      ce977ef5
  4. 23 Jul, 2003 1 commit
  5. 22 Jul, 2003 6 commits
  6. 21 Jul, 2003 3 commits
  7. 19 Jul, 2003 2 commits
  8. 18 Jul, 2003 7 commits
  9. 17 Jul, 2003 1 commit
  10. 16 Jul, 2003 5 commits
  11. 15 Jul, 2003 4 commits
  12. 14 Jul, 2003 2 commits
    • unknown's avatar
      merge · 21721b97
      unknown authored
      
      mysql-test/r/rpl_max_relay_size.result:
        Auto merged
      21721b97
    • unknown's avatar
      Fixed wrong test in LOG::close · 462b47e2
      unknown authored
      Fixed test for binary build
      
      
      mysql-test/r/rpl_max_relay_size.result:
        Fixed test for binary build
      mysql-test/t/rpl_max_relay_size.test:
        Fixed test for binary build
      sql/log.cc:
        Fixed wrong test in close
      462b47e2