- 05 Nov, 2007 1 commit
-
-
aelkin/elkin@koti.dsl.inet.fi authored
refining tests as they appear to be non-deterministic.
-
- 02 Nov, 2007 5 commits
-
-
skozlov/ksm@virtop.localdomain authored
into mysql.com:/home/ksm/commits/mysql-5.1-new-rpl
-
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.1/bug31554-rpl_truncate
-
aelkin/elkin@koti.dsl.inet.fi authored
Actually, the failure happened with 3innodb as well. Most probably the reason is in failing to delete a binlog file on __NT__ so that that master increments the index of the binlog file. The test results hide valueable warning that windows could generate about that. The scope of this fix is to make sure we have such warning and to lessen chances for binlog file being held at time of closing. The dump thread is getting a good chance to leave and release the file for its successful deletion. We shall watch over the two tests as regression is not excluded. In that case we would have an extra info possibly explaining why __NT__ env can not close/delete the file. However, regardless of that reason, there is alwasy workaround to mask out non-deterministic binlog index number.
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-rpl
-
- 31 Oct, 2007 3 commits
-
-
Corrected issues found in preparing to push code
-
jmiller/jbmiller@ndbqa01.mysql.com authored
into mysql.com:/usr/clones/rpl-push
-
aelkin/elkin@koti.dsl.inet.fi authored
destination. Removing wrong (local temp) tests.
-
- 30 Oct, 2007 6 commits
-
-
jmiller/root@ndbqa01.mysql.com authored
into mysql.com:/usr/clones/rpl-push
-
aelkin@dl145j.mysql.com authored
-
aelkin/elkin@koti.dsl.inet.fi authored
involved bug#12691, bug#27571
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/5.1-merge-bug27571
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug27571_asyn_killed_flags
-
bar@bar.myoffice.izhnet.ru authored
into mysql.com:/home/bar/mysql-work/mysql-5.1-new-rpl-merge
-
- 29 Oct, 2007 2 commits
-
-
aelkin/elkin@koti.dsl.inet.fi authored
Query_log_event::error_code A query can perform completely having the local var error of mysql_$query zero, where $query in insert, update, delete, load, and be binlogged with error_code e.g KILLED_QUERY while there is no reason do to so. That can happen because Query_log_event consults thd->killed flag to evaluate error_code. Fixed with implementing a scheme suggested and partly implemented at time of bug@22725 work-on. error_status is cached immediatly after the control leaves the main rows-loop and that instance always corresponds to `error' the local of mysql_$query functions. The cached value is passed to Query_log_event constructor, not the default thd->killed which can be changed in between of the caching and the constructing.
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
- 26 Oct, 2007 3 commits
-
-
mats@kindahl-laptop.dnsalias.net authored
into kindahl-laptop.dnsalias.net:/home/bk/b12691-mysql-5.0-rpl
-
mats@kindahl-laptop.dnsalias.net authored
Adding code to keep skipping events while inside a transaction. Execution will start just after the transaction has been skipped.
-
msvensson@pilot.mysql.com authored
-
- 25 Oct, 2007 3 commits
-
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.1/bug30594-rpl.rpl_skip_error_is_nondeterministic
-
joerg@trift2. authored
to get rid of a name clash among *deleted* files on case-insignificant file systems.
-
sven@murkla.(none) authored
Documented some binlog events using doxygen. More will be done later. Also fixed typos in other comments and added remarks about dubious code. Only comments are affected, there is no change to the actual code.
-
- 24 Oct, 2007 6 commits
-
-
mats@kindahl-laptop.dnsalias.net authored
into kindahl-laptop.dnsalias.net:/home/bk/b24860-mysql-5.1-rpl
-
mats@kindahl-laptop.dnsalias.net authored
replication): Incremental patch to enable idempotency support for update events again. The final handling of errors will be done in BUG#31609, and until then the handling of errors should be consistent between the different types of changes.
-
gluh@mysql.com/eagle.(none) authored
-
bar@bar.myoffice.izhnet.ru authored
into mysql.com:/home/bar/mysql-work/mysql-5.0.b31081
-
bar@mysql.com/bar.myoffice.izhnet.ru authored
Additional fix for valgrind warning
-
bar@bar.myoffice.izhnet.ru authored
into mysql.com:/home/bar/mysql-work/mysql-5.0-rpl-mr
-
- 23 Oct, 2007 11 commits
-
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.1-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my50-30638
-
ssh://bk-internal.mysql.com//home/bk/mysql-5.0-optkaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.0-opt
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/30638/my51-30638
-
kaa@polly.(none) authored
into polly.(none):/home/kaa/src/opt/mysql-5.1-opt
-