- 06 Jan, 2008 1 commit
-
-
hezx@mail.hezx.com authored
into mail.hezx.com:/media/sda3/work/mysql/bkwork/bug#32205/mysql-5.0-rpl
-
- 02 Jan, 2008 1 commit
-
-
sven@riska.(none) authored
into riska.(none):/home/sven/bk/b26395-autocommit-xa/5.0-rpl
-
- 24 Dec, 2007 1 commit
-
-
hezx@mail.hezx.com authored
into mail.hezx.com:/media/sda3/work/mysql/bkwork/bug#28908/mysql-5.0-rpl
-
- 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 8 commits
-
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug33435-load_data_read_buffer_size
-
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
-
sven@riska.(none) authored
Now, every transaction (including autocommit transactions) start with a BEGIN and end with a COMMIT/ROLLBACK in the binlog. Added a test case, and updated lots of test case result files.
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug31359-future_gpos
-
hezx@mail.hezx.com authored
into mail.hezx.com:/media/sda3/work/mysql/bkwork/bug#28908/5.0
-
aelkin/elkin@koti.dsl.inet.fi authored
ignores future_group_master_log_p There was a redundant assignement. However, that's the only artifact. Wrt to future_group_master_log_position, there is no issue. The counter is supposed to be set at Log_event::exec_event(). It's used only by Innodb for recovery purposes.
-
mats@capulet.kindahl.net authored
into capulet.kindahl.net:/home/mats/devel/fix-mysql-5.0-rpl
-
hezx@mail.hezx.com authored
When set the server-id dynamically, the server_id member of current thread is not updated. Update the server_id member of current thread after updated the global variable value.
-
- 20 Dec, 2007 1 commit
-
-
mats@capulet.kindahl.net authored
Complementary patch since LOAD DATA INFILE was not covered in the previous patch. This patch adds a check so that the slave skip counter is not decreased to zero if seeing a BEGIN_LOAD_QUERY_EVENT, APPEND_BLOCK_EVENT, or CREATE_FILE_EVENT since these cannot end a group. The group is terminated by an EXECUTE_LOAD_QUERY_ EVENT or DELETE_FILE_EVENT.
-
- 18 Dec, 2007 1 commit
-
-
hezx@hezx.(none) authored
-
- 15 Dec, 2007 1 commit
-
-
hezx@hezx.(none) authored
The reason of this bug is that when mysqlbinlog dumps a query, the query is written to output with a delimeter appended right after it, if the query string ends with a '--' comment, then the delimeter would be considered as part of the comment, if there are any statements after this query, then it will cause a syntax error. Start a newline before appending delimiter after a query string
-
- 11 Dec, 2007 1 commit
-
-
hezx@hezx.(none) authored
into hezx.(none):/media/hda5/work/mysql/bkwork/bug#30998/5.0
-
- 05 Dec, 2007 1 commit
-
-
bar@mysql.com/bar.myoffice.izhnet.ru authored
Fixing a wrong comment.
-
- 03 Dec, 2007 1 commit
-
-
hezx@hezx.(none) authored
When executing drop view statement on the master, the statement is written into bin-log without checking for possible errors, so the statement would always be bin-logged with error code cleared even if some error might occur, for example, some of the views being dropped does not exist. This would cause failure on the slave. Writing bin-log after check for errors, if at least one view has been dropped the query is bin-logged possible with an error.
-
- 22 Nov, 2007 1 commit
-
-
mats@capulet.kindahl.net authored
into capulet.kindahl.net:/home/bk/mysql-5.0-rpl
-
- 14 Nov, 2007 3 commits
-
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl
-
mats@capulet.net authored
into capulet.net:/home/bk/mysql-5.0-rpl
-
- 13 Nov, 2007 2 commits
-
-
mats@kindahl-laptop.dnsalias.net authored
-
mats@kindahl-laptop.dnsalias.net authored
-
- 12 Nov, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
Corrections to get_str_len_and_pointer().
-
- 10 Nov, 2007 1 commit
-
-
mats@capulet.net authored
-
- 09 Nov, 2007 3 commits
-
-
mats@capulet.net authored
into capulet.net:/home/mats/devel/b31793-mysql-5.0-rpl
-
mats@capulet.net authored
into capulet.net:/home/bk/mysql-5.0-rpl
-
mats@capulet.net authored
When running mysqlbinlog on a 64-bit machine with a corrupt relay log, it causes mysqlbinlog to crash. In this case, the crash is caused because a request for 18446744073709534806U bytes is issued, which apparantly can be served on a 64-bit machine (speculatively, I assume) but this causes the memcpy() issued later to copy the data to segfault. The request for the number of bytes is caused by a computation of data_len - server_vars_len where server_vars_len is corrupt in such a sense that it is > data_len. This causes a wrap-around, with the the data_len given above. This patch adds a check that if server_vars_len is greater than data_len before the substraction, and aborts reading the event in that case marking the event as invalid. It also adds checks to see that reading the server variables does not go outside the bounds of the available space, giving a limited amount of integrity check.
-
- 06 Nov, 2007 7 commits
-
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug27571_asyn_killed_flags
-
aelkin/elkin@koti.dsl.inet.fi authored
refining non-deterministic tests. The new Bug@32148 is in the way. Adjuting the tests to be somehow useful.
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug28597-log_name_upgrade
-
aelkin/elkin@koti.dsl.inet.fi authored
fixing tests
-
aelkin/elkin@koti.dsl.inet.fi authored
removing extra tests (on 5.1 that's been already done)
-
aelkin/elkin@koti.dsl.inet.fi authored
commit is specific for 5.0 to eliminated non-deterministic tests. Those tests run only in 5.1 env where there is a necessary devices such as processlist table of info_schema.
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug27571_asyn_killed_flags
-
- 05 Nov, 2007 3 commits
-
-
malff@lambda.hsd1.co.comcast.net. authored
into lambda.hsd1.co.comcast.net.:/home/malff/TREE/mysql-5.0-rt-merge
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug28597-log_name_upgrade
-
aelkin/elkin@koti.dsl.inet.fi authored
Since bug@20166, which replaced the binlog file name generating to base on pidfile_name instead of the previous glob_hostname, the binlog file name suddenly started to be stored solely in the absolute path format, including a case when --log-bin option meant a relative path. What's more serious, the path for binlog file can lead unrequestedly to pid-file directory so that after any proper fix for this bug there might be similar to the bug report consequences for one who upgrades from post-fix-bug@20166-pre-fix-bug@28597 to post-fix-bug@28597. Fixed with preserving`pidfile_name' (intr.by bug@20166) but stripping off its directory part. This restores the original logics of storing the names in compatible with --log-bin option format and with the requirement for --log-bin ralative path to corresond to the data directory. Side effects for this fix: effective fixing bug@27070, refining its test; ensuring no overrun for buff can happen anymore (Bug#31836 insufficient space reserved for the suffix of relay log file name); bug#31837 --remove_file $MYSQLTEST_VARDIR/tmp/bug14157.sql missed in rpl_temporary.test; fixes Bug@28603 Invalid log-bin default location;
-