- 14 May, 2004 4 commits
-
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
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
-
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
-
unknown authored
innobase/include/ut0mem.h: Remove unused function ut_str_catenate() innobase/ut/ut0mem.c: Remove unused function ut_str_catenate()
-
- 13 May, 2004 8 commits
-
-
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
-
unknown authored
into mysql.com:/space/my/mysql-4.0
-
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
-
unknown authored
into mysql.com:/space/my/mysql-4.0-build
-
unknown authored
make_binary_distribution (bug#2857) scripts/make_binary_distribution.sh: - make sure the binaries are executable before calling them (bug#2857)
-
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
-
unknown authored
innobase/dict/dict0dict.c: dict_index_name_print(): output table name to file, not stderr
-
unknown authored
innobase/os/os0file.c: Remove os_file_lock()
-
- 12 May, 2004 2 commits
- 11 May, 2004 4 commits
-
-
unknown authored
- Tagged ChangeSet@1.1800.1.1 as "mysql-4.0.19" configure.in: - Bumped up version number from 4.0.19 -> 4.0.20
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
unknown authored
-
http://bugs.mysql.comunknown authored
innobase/btr/btr0btr.c: Changed bug reporting address to http://bugs.mysql.com innobase/dict/dict0load.c: Changed bug reporting address to http://bugs.mysql.com innobase/ibuf/ibuf0ibuf.c: Changed bug reporting address to http://bugs.mysql.com innobase/lock/lock0lock.c: Changed bug reporting address to http://bugs.mysql.com innobase/row/row0ins.c: Changed bug reporting address to http://bugs.mysql.com innobase/row/row0sel.c: Changed bug reporting address to http://bugs.mysql.com innobase/row/row0umod.c: Changed bug reporting address to http://bugs.mysql.com innobase/row/row0upd.c: Changed bug reporting address to http://bugs.mysql.com innobase/trx/trx0rec.c: Changed bug reporting address to http://bugs.mysql.com innobase/ut/ut0dbg.c: Changed bug reporting address to http://bugs.mysql.com
-
- 10 May, 2004 7 commits
-
-
unknown authored
into hundin.mysql.fi:/home/marko/j/mysql-4.0
-
unknown authored
innobase/row/row0mysql.c: Compare database part of table name with memcmp(), not strcmp()
-
unknown authored
into mysql.com:/home/mydev/mysql-4.0-bug2831
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
unknown authored
"phrase search" should not match partial words (it should not match 'paraphrase searches')
-
unknown authored
into mysql.com:/home/mydev/mysql-4.0-bug2831
-
unknown authored
mysql-test/t/rpl000015.test: Fix replace_result of $MASTER_MYPORT instead of literal numbers. The test case rpl000015 needs one exlpicit literal number. It changes partial master settings, which seems to reset other settings to their defaults. To test this is obviously the intent of this case.
-
- 07 May, 2004 3 commits
-
-
unknown authored
into hundin.mysql.fi:/home/marko/l/mysql-4.0
-
unknown authored
innobase/row/row0mysql.c: Revert accidental modification to row_lock_table_autoinc_for_mysql() made in ChangeSet@1.1794.1.1 mysql-test/r/innodb.result: Revert ChangeSet@1.1794.1.1
-
unknown authored
into mysql.com:/home/mydev/mysql-4.0-bug2831 BitKeeper/etc/logging_ok: auto-union
-
- 06 May, 2004 7 commits
-
-
unknown authored
into a80-186-24-72.elisa-laajakaista.fi:/home/my/bk/mysql-4.0
-
unknown authored
to use long query strings with it. Bug#3633 BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
myisam/mi_dynrec.c: need DBUG_RETURN as we DBUG_ENTER
-
unknown authored
BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
unknown authored
sql/sql_acl.cc: Auto merged
-
unknown authored
-
- 05 May, 2004 5 commits
-
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
very minor changes: a STOP SLAVE in a replication test to get rid of a non critical message in slave.err, and a comment update mysql-test/r/rpl_server_id2.result: result update mysql-test/t/rpl_server_id2.test: We stop the slave before cleaning up otherwise we'll get 'drop table t1' executed twice, so an error in the slave.err (not critical). sql/slave.cc: update comment about 4.1 now that 4.1 is fixed (in a few minutes, exactly)
-
unknown authored
innobase/include/os0file.h: Add os_file_set_eof() innobase/os/os0file.c: Add os_file_set_eof() innobase/srv/srv0srv.c: Replace chsize() or ftruncate() with os_file_set_eof() sql/ha_innodb.cc: Replace my_chsize() with os_file_set_eof()
-
unknown authored
-
unknown authored
(Bug #3596) innobase/srv/srv0srv.c: Truncate "<datadir>/innodb.status.<pid>" to its actual size (Bug #3596) sql/ha_innodb.cc: Truncate "<datadir>/innodb.status.<pid>" to its actual size (Bug #3596)
-