1. 19 Jul, 2003 1 commit
  2. 01 Jul, 2003 2 commits
  3. 29 Jun, 2003 1 commit
  4. 26 Jun, 2003 2 commits
  5. 21 Jun, 2003 1 commit
    • unknown's avatar
      Can't believe it: one more cset (04-27) which never found his way to the central · 71438155
      unknown authored
      repository (incredible that I forgot to push, but why not).
      So unfortunately the bugfix missed 3.23.57 and will be in .58 :(
      Instead of looking like working (bug #198), replication between
      a 3.23 slave and 4.0 master should frankly stop. Here we detect
      4.0 masters in the 3.23 slave code when we see a strange Rotate
      event, and in that case we print an error and stop.
      4.0.13 and older masters will be "often" caught (see the patch); 4.0.14
      and newer masters will always be immediately caught.
      
      
      sql/slave.cc:
        Instead of looking like working (bug #198), replication between
        a 3.23 slave and 4.0 master should frankly stop. Here we detect
        4.0 masters in the 3.23 slave code when we see a strange Rotate
        event, and in that case we print an error and stop.
        4.0.13 and older masters will be "often" caught (see the patch); 4.0.14
        and newer masters will always be immediately caught.
      71438155
  6. 19 Jun, 2003 2 commits
  7. 18 Jun, 2003 3 commits
  8. 16 Jun, 2003 2 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-3.23 · 714bf070
      unknown authored
      into mysql.com:/home/mysql_src/mysql-3.23
      
      
      714bf070
    • unknown's avatar
      Do not use 'created' for time anymore in Start_log_event, it's the same · 418fcdf1
      unknown authored
      as the already-stored timestamp. Now 'created' is used only to know if
      this is a first binlog or not. And we may re-use the superfluous bytes
      in 5.0 when we need room.
      
      
      sql/log_event.cc:
        This sort of reverts a change I made in 3.23.57. In 3.23.57 I set 'created' to 0
        if this was a non-first binlog, so I made mysqlbinlog not print the "created xx"
        part if created == 0. While this was sensible, as 'created' is 0 or equal to
        the timestamp which is already stored in the event, we can always print
        "created xx" by using the timestamp, and leaving the use of 'created' only to
        know if this is a first binlog or not (which we print as "created at startup").
      sql/log_event.h:
        In Start_log_event, 'created' is always the same as 'when', or O.
        We didn't need 4 bytes for this, a bit would have been enough (O or
        "same as 'when'"). Possibly in 5.0 we will re-use the useless bytes.
      418fcdf1
  9. 11 Jun, 2003 1 commit
    • unknown's avatar
      os0file.c: · a18c4883
      unknown authored
        Prevent on Windows starting of two mysqld instances on SAME InnoDB files: that could cause severe database corruption
      
      
      innobase/os/os0file.c:
        Prevent on Windows starting of two mysqld instances on SAME InnoDB files: that could cause severe database corruption
      a18c4883
  10. 08 Jun, 2003 1 commit
    • unknown's avatar
      Translation updated · 87473e96
      unknown authored
      
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      87473e96
  11. 07 Jun, 2003 1 commit
    • unknown's avatar
      page0page.c: · e5ae26c7
      unknown authored
        Fix a bug: a race condition could cause that the first B-tree page splits would get a corrupt page directory, whic often results in the assertion in page_dir_find_slot(); found with a test of 3000 startups/shutdowns; it is not clear that this would have caused any corruption which users have reported
      
      
      innobase/page/page0page.c:
        Fix a bug: a race condition could cause that the first B-tree page splits would get a corrupt page directory, whic often results in the assertion in page_dir_find_slot(); found with a test of 3000 startups/shutdowns; it is not clear that this would have caused any corruption which users have reported
      e5ae26c7
  12. 06 Jun, 2003 2 commits
    • unknown's avatar
      In Start_log_event::print, don't print "created 1970 etc" if created == 0. · 07d6a199
      unknown authored
      Otherwise, we'll get questions from users about this curious 1970.
      
      
      07d6a199
    • unknown's avatar
      -- already approved; it would be nice if it goes into 3.23.57 -- · 98f57fbe
      unknown authored
      Fix for bug 254 : the first Start_log_event after server startup will
      have created=now(), whereas the next ones (FLUSH LOGS, auto rotation)
      will have created=0. Before this, it was always now().
      This way, slaves >=4.0.14 will know when they must
      drop stale temp tables or not. The next task is now modify 4.0.14 to
      implement this.
      
      
      sql/log.cc:
        Fix for bug 254 : the first Start_log_event after server startup will
        have created=now(), whereas the next ones (FLUSH LOGS, auto rotation)
        will have created=0. Before this, it was always now().
        This way, slaves >=4.0.14 will know when they must
        drop stale temp tables or not.
      sql/log_event.h:
        An explanation.
      sql/sql_class.h:
        Prototype change (see log.cc).
      98f57fbe
  13. 05 Jun, 2003 2 commits
  14. 31 May, 2003 2 commits
  15. 28 May, 2003 1 commit
    • unknown's avatar
      srv0srv.c: · 936a8aec
      unknown authored
        Prevent the InnoDB main thread from hogging CPU if a table lingers in the background drop queue (though it is essentially a bug if a table end up there at all)
      
      
      innobase/srv/srv0srv.c:
        Prevent the InnoDB main thread from hogging CPU if a table lingers in the background drop queue (though it is essentially a bug if a table end up there at all)
      936a8aec
  16. 27 May, 2003 1 commit
  17. 26 May, 2003 6 commits
  18. 23 May, 2003 1 commit
  19. 21 May, 2003 2 commits
  20. 14 May, 2003 4 commits
  21. 07 May, 2003 2 commits