- 16 Sep, 2007 1 commit
-
-
aelkin@dl145j.mysql.com authored
-
- 15 Sep, 2007 1 commit
-
-
aelkin@dl145j.mysql.com authored
into dl145j.mysql.com:/tmp/andrei/5.1-merge
-
- 14 Sep, 2007 2 commits
-
-
cbell/Chuck@mysql_cab_desk. authored
into mysql_cab_desk.:C:/source/c++/mysql-5.1_BUG_30790
-
cbell/Chuck@mysql_cab_desk. authored
This patch clarifies some of the coding choices with documentationa and removes a limitation in the code for future expansion of the CHAR and BINARY fields to length > 255.
-
- 07 Sep, 2007 1 commit
-
-
- 04 Sep, 2007 1 commit
-
-
rafal@quant.(none) authored
-
- 30 Aug, 2007 1 commit
-
-
aelkin/elkin@koti.dsl.inet.fi authored
into koti.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.0/bug30209-rpl_packet_mismatch_by_kaamos
-
- 29 Aug, 2007 5 commits
-
-
aelkin/elkin@koti.dsl.inet.fi authored
explicit --sleep is removed in favor of wait_for_slave_io_to_stop.inc. The status reporting uses `SHOW SLAVE STATUS' *not* possibly buggy "SHOW STATUS LIKE 'Slave_running'".
-
mats@kindahl-laptop.dnsalias.net authored
into kindahl-laptop.dnsalias.net:/home/bk/b29968-mysql-5.1-rpl
-
mats@kindahl-laptop.dnsalias.net authored
into kindahl-laptop.dnsalias.net:/home/bk/b29968-merge-5.1-rpl
-
mats@kindahl-laptop.dnsalias.net authored
Removing unguarded read of slave_running field from inside terminate_slave_threads(). This could cause premature exit in the event that the slave thread already were shutting down, but isn't finished yet. The fields slave_running, io_thd, and sql_thread are guarded by an associated run_lock. A read of these fields were not guarded inside terminate_slave_threads(), which caused an assertion to fire. The assertion was removed, and the code reorganized slightly.
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bk/mysql-5.0-bug21132
-
- 28 Aug, 2007 1 commit
-
-
skozlov/ksm@virtop.localdomain authored
into mysql.com:/home/ksm/commits/mysql-5.1-new-rpl-2
-
- 27 Aug, 2007 5 commits
-
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bk/mysql-5.1-bug21842-rpl
-
rafal@quant.(none) authored
table->record[1] buffers inside Rows_log_event::find_row() function. The patch fixes this.
-
Bug#29020 Event results not correctly replicated to slave in RBR: partially.
-
rafal@quant.(none) authored
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bk/mysql-5.1-bug21842-rpl
-
- 26 Aug, 2007 1 commit
-
-
rafal@quant.(none) authored
using TPC-B): Problem: A RBR event can contain incomplete row data (only key value and fields which have been changed). In that case, when the row is unpacked into record and written to a table, the missing fields get incorrect NULL values leading to master-slave inconsistency. Solution: Use values found in slave's table for columns which are not given in the rows event. The code for writing a single row uses the following algorithm: 1. unpack row_data into table->record[0], 2. try to insert record, 3. if duplicate record found, fetch it into table->record[0], 4. unpack row_data into table->record[0], 5. write table->record[0] into the table. Where row_data is the row as stored in the data area of a rows event. Thus: a) unpacking of row_data happens at the time when row is written into a table, b) when unpacking (in step 4), only columns present in row_data are overwritten - all other columns remain as they were found in the table. Since all data needed for the above algorithm is stored inside Rows_log_event class, functions which locate and write rows are turned into methods of that class. replace_record() -> Rows_log_event::write_row() find_and_fetch_row() -> Rows_log_event::find_row() Both methods take row data from event's data buffer - the row being processed is pointed by m_curr_row. They unpack the data as needed into table's record buffers record[0] or record[1]. When row is unpacked, m_curr_row_end is set to point at next row in the data buffer. Other changes introduced in this changeset: - Change signature of unpack_row(): don't report errors and don't setup table's rw_set here. Errors can happen only when setting default values in prepare_record() function and are detected there. - In Rows_log_event and derived classes, don't pass arguments to the execution primitives (do_...() member functions) but use class members instead. - Move old row handling code into log_event_old.cc to be used by *_rows_log_event_old classes. Also, a new test rpl_ndb_2other is added which tests basic replication from master using ndb tables to slave storing the same tables using (possibly) different engine (myisam,innodb). Test is based on existing tests rpl_ndb_2myisam and rpl_ndb_2innodb. However, these tests doesn't work for various reasons and currently are disabled (see BUG#19227). The new test differs from the ones it is based on as follows: 1. Single test tests replication with different storage engines on slave (myisam, innodb, ndb). 2. Include file extra/rpl_tests/rpl_ndb_2multi_eng.test containing original tests is replaced by extra/rpl_tests/rpl_ndb_2multi_basic.test which doesn't contain tests using partitioned tables as these don't work currently. Instead, it tests replication to a slave which has more or less columns than master. 3. Include file include/rpl_multi_engine3.inc is replaced with include/rpl_multi_engine2.inc. The later differs by performing slightly different operations (updating more than one row in the table) and clearing table with "TRUNCATE TABLE" statement instead of "DELETE FROM" as replication of "DELETE" doesn't work well in this setting. 4. Slave must use option --log-slave-updates=0 as otherwise execution of replication events generated by ndb fails if table uses a different storage engine on slave (see BUG#29569).
-
- 22 Aug, 2007 5 commits
-
-
antony@pcg5ppc.xiphis.org authored
"Test federated_bug_25714 issues non-existing shell command" Problem caused by missing '$' symbol in eval statement causing it to always attempt to run test even if the test was not compiled.
-
joerg@trift2. authored
-
joerg@trift2. authored
into trift2.:/MySQL/M51/target-5.1.22
-
fixing the test due a to different offsets in binlog with ps-protocol (a possible bug to be reported)
-
refining of cleanup of the tests.
-
- 21 Aug, 2007 2 commits
-
-
uncommented the test case stated in bug18856 and commiting to mysql-5.1-target-5.1.22 clone per Tomas
-
Binlogging of the statement with a side effect like a modified non-trans table did not happen. The artifact involved all binloggable dml queries. Fixed with changing the binlogging conditions all over the code to exploit thd->transaction.stmt.modified_non_trans_table introduced by the patch for bug@27417. Multi-delete case has own specific addressed by another bug@29136. Multi-update case has been addressed by bug#27716 and patch and will need merging.
-
- 20 Aug, 2007 4 commits
-
-
jbruehe/mysqldev@suse9-x86.mysql.com authored
-
jmiller/ndbdev@ndb08.mysql.com authored
into mysql.com:/data2/mysql-5.1-new-rpl-30128-30209
-
-
-
- 17 Aug, 2007 4 commits
-
-
jmiller/ndbdev@ndb08.mysql.com authored
into mysql.com:/data2/mysql-5.1-new-rpl-30128-30209
-
Removed sleep from test per lars request
-
mats@kindahl-laptop.dnsalias.net authored
-
mats@kindahl-laptop.dnsalias.net authored
into kindahl-laptop.dnsalias.net:/home/bk/fix-mysql-5.1-rpl
-
- 16 Aug, 2007 6 commits
-
-
-
into mysql.com:/data0/mysqldev/my/build-200708161639-5.1.21-beta/mysql-5.1-release
-
-
into mysql.com:/data0/mysqldev/my/mysql-5.1-30367
-
-
monty@mysql.com/narttu.mysql.fi authored
Fixed failing func_misc test for embedded server Added casts to avoid compiler warnings Removed Table_locks_immediate as it's depending on log file cacheing Changed type of get_time() to avoid warnings Removed testing if purger master logs succeded as this is not deterministic
-