1. 14 May, 2004 4 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · b2d2dd5c
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      b2d2dd5c
    • unknown's avatar
      Replication testsuite: making the master-slave synchronization less likely to fail, · 190b3a25
      unknown authored
      by adding sleep-and-retries (max 4 times) if MASTER_POS_WAIT() returns NULL
      in sync_with_master and sync_slave_with_master.
      The problem showed up only today, in MySQL 5.0 in rpl_server_id2.test,
      but may affect 4.x as well, so fixing it here. Note that I am also fixing
      5.0 too, with the same exact patch, because I don't want to leave 5.0 broken
      until the next 4.0->4.1->5.0 merge.
      
      
      client/mysqltest.c:
        in sync_with_master (and sync_slave_with_master), if MASTER_POS_WAIT() returns NULL,
        it may be that the slave SQL thread did not have time to start yes, so we sleep
        1 sec and retry, 4 times at most.
      mysql-test/r/rpl_server_id2.result:
        result update
      mysql-test/t/rpl_server_id2.test:
        master_slave.inc already drops the table
      190b3a25
    • unknown's avatar
      Many files: · aecddd8e
      unknown authored
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      
      
      sql/sql_class.h:
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      sql/ha_innodb.cc:
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      sql/log_event.cc:
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      sql/slave.cc:
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      sql/sql_db.cc:
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      sql/sql_parse.cc:
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      sql/sql_show.cc:
        Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query
      aecddd8e
    • unknown's avatar
      InnoDB: Remove unused function ut_str_catenate() · 80264cb0
      unknown authored
      
      innobase/include/ut0mem.h:
        Remove unused function ut_str_catenate()
      innobase/ut/ut0mem.c:
        Remove unused function ut_str_catenate()
      80264cb0
  2. 13 May, 2004 8 commits
    • unknown's avatar
      ha_innodb.cc, trx0trx.h, lock0lock.c, trx0trx.c: · 961cd760
      unknown authored
      Reserve the MySQL LOCK_thread_count mutex when printing thd->query of
      an arbitrary transaction; if we are printing thd->query of a transaction that
      we know is currently executing inside InnoDB, then we know that MySQL cannot
      meanwhile change thd->query, and no need to reserve the MySQL mutex; note
      that this patch still leaves open the possibility of races in MySQL's
      thd->query_len
      
      
      innobase/trx/trx0trx.c:
        Reserve the MySQL LOCK_thread_count mutex when printing thd->query of an arbitrary transaction; if we are printing thd->query of the a transaction that we know is currently executing inside InnoDB, then we know that MySQL cannot meanwhile change thd->query, and no need to reserve the MySQL mutex; note that thsi patch still leaves aopen the possibility of races in MySQL's thd->query_len
      innobase/lock/lock0lock.c:
        Reserve the MySQL LOCK_thread_count mutex when printing thd->query of an arbitrary transaction; if we are printing thd->query of the a transaction that we know is currently executing inside InnoDB, then we know that MySQL cannot meanwhile change thd->query, and no need to reserve the MySQL mutex; note that thsi patch still leaves aopen the possibility of races in MySQL's thd->query_len
      innobase/include/trx0trx.h:
        Reserve the MySQL LOCK_thread_count mutex when printing thd->query of an arbitrary transaction; if we are printing thd->query of the a transaction that we know is currently executing inside InnoDB, then we know that MySQL cannot meanwhile change thd->query, and no need to reserve the MySQL mutex; note that thsi patch still leaves aopen the possibility of races in MySQL's thd->query_len
      sql/ha_innodb.cc:
        Reserve the MySQL LOCK_thread_count mutex when printing thd->query of an arbitrary transaction; if we are printing thd->query of the a transaction that we know is currently executing inside InnoDB, then we know that MySQL cannot meanwhile change thd->query, and no need to reserve the MySQL mutex; note that thsi patch still leaves aopen the possibility of races in MySQL's thd->query_len
      961cd760
    • unknown's avatar
      Merge lgrimmer@build.mysql.com:/home/bk/mysql-4.0 · e58e8a1b
      unknown authored
      into mysql.com:/space/my/mysql-4.0
      
      e58e8a1b
    • unknown's avatar
      ha_innodb.cc: · d6360496
      unknown authored
        A flawed fix of the thd->query race in SHOW INNODB STATUS; see the comments in code about how to fix this properly; we cannot use LOCK_thread_count to protect thd->query, because that will cause a deadlock of threads
      
      
      sql/ha_innodb.cc:
        A flawed fix of the thd->query race in SHOW INNODB STATUS; see the comments in code about how to fix this properly; we cannot use LOCK_thread_count to protect thd->query, because that will cause a deadlock of threads
      d6360496
    • unknown's avatar
      Merge mysql.com:/space/my/mysql-4.0 · bddf10f5
      unknown authored
      into mysql.com:/space/my/mysql-4.0-build
      
      bddf10f5
    • unknown's avatar
      - make sure the binaries are executable before calling them during · 8d5fb1a3
      unknown authored
         make_binary_distribution (bug#2857)
      
      
      scripts/make_binary_distribution.sh:
         - make sure the binaries are executable before calling them (bug#2857)
      8d5fb1a3
    • unknown's avatar
      ha_innodb.cc: · 568b6cfa
      unknown authored
        innobase_mysql_print_thd(): protect thd with LOCK_thread_count (Bug #3596)
      
      
      sql/ha_innodb.cc:
        innobase_mysql_print_thd(): protect thd with LOCK_thread_count
      568b6cfa
    • unknown's avatar
      InnoDB: fixed bug in dict0dict.c: dict_index_name_print() · 7aa4652d
      unknown authored
      
      innobase/dict/dict0dict.c:
        dict_index_name_print(): output table name to file, not stderr
      7aa4652d
    • unknown's avatar
      InnoDB: Remove os_file_lock() from the 4.0 tree (unfix Bug #3608) · 1fbd375c
      unknown authored
      
      innobase/os/os0file.c:
        Remove os_file_lock()
      1fbd375c
  3. 12 May, 2004 2 commits
  4. 11 May, 2004 4 commits
  5. 10 May, 2004 7 commits
  6. 07 May, 2004 3 commits
  7. 06 May, 2004 7 commits
  8. 05 May, 2004 5 commits