- 30 May, 2007 12 commits
-
-
into dsl-hkibras1-ff5dc300-70.dhcp.inet.fi:/home/elkin/MySQL/TEAM/BARE/mysql-5.1-new-rpl
-
bar@mysql.com/bar.myoffice.izhnet.ru authored
Adding strnlen.c into the list of source files.
-
fixing FD event issue that showed up on pb.
-
bar@bar.myoffice.izhnet.ru authored
into mysql.com:/home/bar/mysql-5.1.b28558
-
bar@mysql.com/bar.myoffice.izhnet.ru authored
-
Fixed test case rpl_incident.test (synchronize drop table, masked IO thread behaviour)
-
bar@mysql.com/bar.myoffice.izhnet.ru authored
The source of the problem was in my_vsnprintf() implementation.
-
Merge dsl-hkibras1-ff5dc300-70.dhcp.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.1/bug27044_slave_dup2unique into dsl-hkibras1-ff5dc300-70.dhcp.inet.fi:/tmp/merge_5.0
-
merge 5.0 with 5.1
-
into dsl-hkibras1-ff5dc300-70.dhcp.inet.fi:/tmp/merge_5.0
-
test comments correction
-
into dsl-hkibras1-ff5dc300-70.dhcp.inet.fi:/tmp/merge_5.0
-
- 29 May, 2007 8 commits
-
-
combining the final result variable in such way that either option of the test execution will yield zero.
-
tests refining, see binlog_killed.test file for details
-
merge with 5.0
-
into dsl-hkibras1-ff5dc300-70.dhcp.inet.fi:/tmp/merge_5.0
-
refining the test.
-
result file updated
-
The bug in that slave version of a table with unique field still was able to execute INSERT query as replace whereas it's impossible on master. The reason of this artifact is wrong usage of ndb->extra:s. Fixed with resetting flags at do_after. There is open issue with symmetrical resetting table->file->extra(HA_EXTRA_NO_IGNORE_NO_KEY) which i had to hand to bug#27077. The test for the current bug was committed in a cset for bug#27320.
-
Refining the tests since pb revealed the older version's fragality - the error from SF() due to killed may be different on different env:s. DBUG_ASSERT instead of assert.
-
- 28 May, 2007 6 commits
-
-
into dsl-hkibras1-ff5dc300-70.dhcp.inet.fi:/tmp/merge_5.0
-
The reason for the bug was that replaying of a query on slave could not be possible since its event was recorded with the killed error. Due to the specific of handling INSERT, which per-row-while-loop is unbreakable to killing, the query on transactional table should have not appeared in binlog unless there was a call to a stored routine that got interrupted with killing (and then there must be an error returned out of the loop). The offered solution added the following rule for binlogging of INSERT that accounts the above specifics: For INSERT on transactional-table if the error was not set the only raised flag is harmless and is ignored via masking out on time of creation of binlog event. For both table types the combination of raised error and KILLED flag indicates that there was potentially partial execution on master and consistency is under the question. In that case the code continues to binlog an event with an appropriate killed error. The fix relies on the specified behaviour of stored routine that must propagate the error to the top level query handling if the thd->killed flag was raised in the routine execution. The patch adds an arg with the default killed-status-unset value to Query_log_event::Query_log_event.
-
-
lars/lthalmann@dl145k.mysql.com authored
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.1-merge
-
lars/lthalmann@dl145h.mysql.com authored
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.1-merge
-
lars/lthalmann@dl145h.mysql.com authored
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
- 24 May, 2007 10 commits
-
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build-work
-
lars/lthalmann@dl145h.mysql.com authored
into mysql.com:/nfsdisk1/lars/bk/mysql-5.1-new-rpl
-
- 23 May, 2007 4 commits
-
-
bar@mysql.com/bar.myoffice.izhnet.ru authored
As MySQL character set tests can print results in many character sets (latin1, utf8-8, sjis, cp932 and others) - its output can be incompatible with the current locale settings, which makes PERL confuse. Fix: reset LC_ALL and LC_CTYPE to "C", which is compatible with any character set.
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-