1. 24 Jul, 2003 2 commits
    • unknown's avatar
      Fix for BUG#858 "CHANGE MASTER forgets to update relay-log.info"; · 14d9a2e5
      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).
      14d9a2e5
    • unknown's avatar
      WL#1036 (print the db in slave error messages). · ab34adf6
      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.
      ab34adf6
  2. 21 Jul, 2003 1 commit
  3. 19 Jul, 2003 2 commits
  4. 18 Jul, 2003 7 commits
  5. 17 Jul, 2003 1 commit
  6. 16 Jul, 2003 5 commits
  7. 15 Jul, 2003 4 commits
  8. 14 Jul, 2003 13 commits
    • unknown's avatar
      merge · c36c37c3
      unknown authored
      
      mysql-test/r/rpl_max_relay_size.result:
        Auto merged
      c36c37c3
    • unknown's avatar
      Fixed wrong test in LOG::close · e97b2766
      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
      e97b2766
    • unknown's avatar
      Added missing --replace_result for ports in SHOW SLAVE STATUS. · 45db29db
      unknown authored
      
      mysql-test/r/rpl_max_relay_size.result:
        result update
      mysql-test/t/rpl_max_relay_size.test:
        port-independent test
      45db29db
    • unknown's avatar
      errmsg.txt: · aa70f482
      unknown authored
        Correct a misleading error message about max row length
      
      
      sql/share/english/errmsg.txt:
        Correct a misleading error message about max row length
      aa70f482
    • unknown's avatar
      ha_innodb.h: · 66672ad1
      unknown authored
        Revert the previous patch: MySQL would not allow creation of VARCHAR columns whose total max length is > 8000 bytes, though InnoDB can easily store them as trailing spaces are removed
      
      
      sql/ha_innodb.h:
        Revert the previous patch: MySQL would not allow creation of VARCHAR columns whose total max length is > 8000 bytes, though InnoDB can easily store them as trailing spaces are removed
      66672ad1
    • unknown's avatar
      ha_innodb.h: · 666d4717
      unknown authored
        Fix wrong error message: If one tried to create table with a very big row len, MySQL claimed the max len is 64 kB for InnoDB, while it normally is 8000 bytes
      
      
      sql/ha_innodb.h:
        Fix wrong error message: If one tried to create table with a very big row len, MySQL claimed the max len is 64 kB for InnoDB, while it normally is 8000 bytes
      666d4717
    • unknown's avatar
      Better fix for bug #791: At binlog rotation, INSERTs may not find their way into the binlog · 128feded
      unknown authored
      
      mysql-test/t/rpl_flush_log_loop.test:
        Add timer to avoid problem when 'flush logs' is executed before we have read all data from master
      sql/log.cc:
        Better fix for bug #791:
        Mark log as LOG_TO_BE_OPENED instead of LOG_CLOSED when it's closed and opened.
      sql/mysqld.cc:
        Better startup message
      sql/slave.cc:
        Fix argument to close()
      sql/sql_class.h:
        Better handling of log.close()
      128feded
    • unknown's avatar
      Proposed bugfix for #712 · 02808985
      unknown authored
      Monty revoked any locks for temporary tables in
      ha_myisam::external_lock()
      But further code bans using write cache on nonlocked tables
      this makes operations much slower
      
      
      myisam/mi_locking.c:
        Handling of MI_TEMPORARY_TABLE lock
      myisam/myisamdef.h:
        defining of MI_TEMPORARY_TABLE
      sql/ha_myisam.cc:
        now we lock temporary tables using MI_TEMPORARY_TABLE lock
      02808985
    • unknown's avatar
      Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-4.0 · c4daa716
      unknown authored
      into mysql.r18.ru:/usr/home/ram/work/4.0
      
      
      c4daa716
    • unknown's avatar
      e45b9ab4
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · 3611f70a
      unknown authored
      into mashka.mysql.fi:/home/my/mysql-4.0
      
      
      3611f70a
    • unknown's avatar
      Safety and speedup fixes: · e1a30696
      unknown authored
      Changed is_open() to work as before.
      Added back inited argument to LOG
      
      
      mysql-test/r/rpl_flush_log_loop.result:
        Fixed results (probably bug in previous rpatch)
      sql/handler.cc:
        Changed is_open() to work as before
      sql/item_func.cc:
        Changed is_open() to work as before
      sql/log.cc:
        Part revert of previous patch.
        The reason for adding back 'inited' is that is that we can't be 100 % sure that init_pthread_objects() is called before mysqld dies (for example on windows)
        I removed mutex lock handling in is_open() as the new code didn't have ANY affect except beeing slower.
        Added back checking of is_open() to some functions as we don't want to do a mutex lock when we are not using logging.
        Indentation/comment fixes
      sql/log_event.cc:
        Changed is_open() to work as before
      sql/repl_failsafe.cc:
        Changed is_open() to work as before
      sql/sql_base.cc:
        Changed is_open() to work as before
      sql/sql_class.h:
        Changed is_open() to work as before. Added back 'inited' variable
      sql/sql_db.cc:
        Changed is_open() to work as before
      sql/sql_delete.cc:
        Changed is_open() to work as before
      sql/sql_insert.cc:
        Changed is_open() to work as before
      sql/sql_load.cc:
        Changed is_open() to work as before
      sql/sql_parse.cc:
        Changed is_open() to work as before
      sql/sql_rename.cc:
        Changed is_open() to work as before
      sql/sql_repl.cc:
        Changed is_open() to work as before
      sql/sql_table.cc:
        Changed is_open() to work as before
      sql/sql_update.cc:
        Changed is_open() to work as before
      e1a30696
    • unknown's avatar
      Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-4.0 · c4381bb0
      unknown authored
      into mysql.r18.ru:/usr/home/ram/work/4.0
      
      
      c4381bb0
  9. 13 Jul, 2003 2 commits
    • unknown's avatar
      srv0srv.c: · d1b9076e
      unknown authored
        Put back a 50 millisecond sleep in too high concurrency situations which I removed in the previous push; count also such sleeping threads to the InnoDB queue in SHOW INNODB STATUS
      
      
      innobase/srv/srv0srv.c:
        Put back a 50 millisecond sleep in too high concurrency situations which I removed in the previous push; count also such sleeping threads to the InnoDB queue in SHOW INNODB STATUS
      d1b9076e
    • unknown's avatar
      srv0srv.c: · 706dc59f
      unknown authored
        Fix a benign bug introduced in 4.0.14: InnoDB could complain 'Error: trying to declare trx to enter InnoDB' if several threads tried to init the auto-inc counter for the same table at the same time; in theory, the bug could even lead to a hang of the server, but that shuld be extremely improbable
      
      
      innobase/srv/srv0srv.c:
        Fix a benign bug introduced in 4.0.14: InnoDB could complain 'Error: trying to declare trx to enter InnoDB' if several threads tried to init the auto-inc counter for the same table at the same time; in theory, the bug could even lead to a hang of the server, but that shuld be extremely improbable
      706dc59f
  10. 12 Jul, 2003 3 commits
    • unknown's avatar
      srv0start.c, srv0srv.h, os0file.h, os0file.c: · bc479783
      unknown authored
        Allow also O_DIRECT as innodb_flush_method; it only affects writing to data files
      
      
      innobase/os/os0file.c:
        Allow also O_DIRECT as innodb_flush_method; it only affects writing to data files
      innobase/include/os0file.h:
        Allow also O_DIRECT as innodb_flush_method; it only affects writing to data files
      innobase/include/srv0srv.h:
        Allow also O_DIRECT as innodb_flush_method; it only affects writing to data files
      innobase/srv/srv0start.c:
        Allow also O_DIRECT as innodb_flush_method; it only affects writing to data files
      bc479783
    • unknown's avatar
      perror.c: · 91eb7ce1
      unknown authored
        fix typo.
      
      
      extra/perror.c:
        fix typo.
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      91eb7ce1
    • unknown's avatar
      Cleaning after removing LOG_INFO_PURGE_NO_ROTATE. · 9480ec82
      unknown authored
      
      sql/sql_repl.cc:
        In my previous change I removed 'no_rotate' from MYSQL_LOG, so this made
        LOG_INFO_PURGE_NO_ROTATE useless (an error code which was never returned),
        so I remove it of the 'switch'.
      9480ec82