An error occurred fetching the project authors.
- 18 Jul, 2008 1 commit
-
-
Sven Sandberg authored
Problem: master binlog has 'create table t1'. Master binlog was removed before slave could replicate it. In test's cleanup code, master did 'drop table t1', which caused slave sql thread to stop with an error since slave sql thread did not know about t1. Fix: t1 is just an auxiliary construction, only needed on master. Hence, we turn off binlogging before t1 is created, drop t1 as soon as we don't need it anymore, and then turn on binlogging again.
-
- 31 Jan, 2008 2 commits
-
-
mkindahl@dl145h.mysql.com authored
-
hezx@mail.hezx.com authored
-
- 30 Jan, 2008 1 commit
-
-
mkindahl@dl145h.mysql.com authored
-
- 23 Dec, 2007 1 commit
-
-
aelkin/elkin@koti.dsl.inet.fi authored
changes due to non-determinism in value of read_buffer_size.
-
- 22 Dec, 2007 1 commit
-
-
aelkin/elkin@koti.dsl.inet.fi authored
refining the test after it failed on pb.
-
- 21 Dec, 2007 1 commit
-
-
aelkin/elkin@koti.dsl.inet.fi authored
read_buffer_size set on master BUG#33413 show binlog events fails if binlog has event size of close to max_allowed_packet The size of Append_block replication event was determined solely by read_buffer_size whereas the rest of replication code deals with max_allowed_packet. When the former parameter was set to larger than the latter there were two artifacts: the master could not read events from binlog; show master events did not show. Fixed with - fragmenting the used io-cached buffer into pieces each size of less than max_allowed_packet (bug#30435) - incrementing show-binlog-events handling thread's max_allowed_packet with the max estimated for the replication header size
-