- 25 Aug, 2003 3 commits
-
-
guilhem@mysql.com authored
Don't start the SQL slave thread with SQL_BIG_SELECTS; it's better to inhibate max_join_size instead.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
For example the Binlog_dump thread (on the master) sometimes showed "Slave:". And there were confusing messages where "binlog" was employed instead of "relay log".
-
- 24 Aug, 2003 1 commit
-
-
heikki@hundin.mysql.fi authored
strerror() does not work in Windows
-
- 23 Aug, 2003 3 commits
-
-
guilhem@mysql.com authored
OPTION_BIG_SELECTS.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
when the SQL thread stops, set rli->inside_transaction to 0. This is needed if the user later restarts replication from a completely different place where there are only autocommit statements. * Detect the case where the master died while flushing the binlog cache to the binlog and stop with error. Cannot add a testcase for this in 4.0 (I tested it manually) as the slave always runs with --skip-innodb.
-
- 22 Aug, 2003 6 commits
-
-
Sinisa@sinisa.nasamreza.org authored
-
Sinisa@sinisa.nasamreza.org authored
Fix for a bug #878
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
fix for BUG#1113 "INSERT into non-trans table SELECT ; ROLLBACK" does not send warning" and fix for BUG#873 "In transaction, INSERT to non-trans table is written too early to binlog". Now we don't always write the non-trans update immediately to the binlog; if there is something in the binlog cache we write it to the binlog cache (because the non-trans update could depend on a trans table which was modified earlier in the transaction); then in case of ROLLBACK, we write the binlog cache to the binlog, wrapped with BEGIN/ROLLBACK. This guarantees that the slave does the same updates. For ROLLBACK TO SAVEPOINT: when we execute a SAVEPOINT command we write it to the binlog cache. At ROLLBACK TO SAVEPOINT, if some non-trans table was updated, we write ROLLBACK TO SAVEPOINT to the binlog cache; when the transaction terminates (COMMIT/ROLLBACK), the binlog cache will be flushed to the binlog (because of the non-trans update) so we'll have SAVEPOINT and ROLLBACK TO SAVEPOINT in the binlog. Apart from this rare case of updates of mixed table types in transaction, the usual way is still clear the binlog cache at ROLLBACK, or chop it at ROLLBACK TO SAVEPOINT (meaning the SAVEPOINT command is also chopped, which is fine). Note that BUG#873 encompasses subbugs 1) and 2) of BUG#333 "3 binlogging bugs when doing INSERT with mixed InnoDB/MyISAM".
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.0
-
monty@narttu.mysql.fi authored
Move test that uses many tables (in query_cache.test) to separate test so that we can get it 'skipped' instead of 'failed' on system where we can't open many files.
-
- 21 Aug, 2003 10 commits
-
-
serg@serg.mylan authored
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
lenz@mysql.com authored
the embedded server (it was missing in the previous push)
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
-
guilhem@mysql.com authored
Let's say the lack of comments did not help me ;) Copying it back again and adding comments; now 3.23->4.0 replication of LOAD DATA INFILE works again.
-
- 20 Aug, 2003 12 commits
-
-
guilhem@mysql.com authored
Since my changes, rpl_log.test, whose result file depends on file_id, became non-repeatable, i.e. file_id on slave in SHOW BINLOG EVENTS changed depending on the order of tests (sometimes 1, sometimes 5). Which is logical: as now the slave does not copy Create_file and Exec_load from the relay log (i.e from the master's binlog) to the slave's binlog, but instead lets mysql_load() do the logging, the file_id is now the one whic was used on the slave. Before it was the one which was used on the master, and by chance the master was always restarted for this test because there's a -master.opt file, so file_id on the master is always 1. But now file_id is from the slave so we need to restart the slave. That's why I add an (empty) -slave.opt file. I could have used 'server_stop/start slave', but this would have required the manager, so most of the time mysql-test-run silently skip the test which makes it useless. And I want this test to be run !
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
"LOAD DATA INFILE is badly filtered by binlog-*-db rules". There will probably be a second final one to merge Dmitri's changes to rpl_log.result and mine. 2 new tests: rpl_loaddata_rule_m : test of logging of LOAD DATA INFILE when the master has binlog-*-db rules, rpl_loaddata_rule_s : test of logging of LOAD DATA INFILE when the slave has binlog-*-db rules and --log-slave-updates.
-
Sinisa@sinisa.nasamreza.org authored
Merge fix
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-4.0-bg-1086
-
monty@narttu.mysql.fi authored
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-4.0-bg-1086
-
monty@narttu.mysql.fi authored
Set min value of max_allowed_packet to 1024 Fixed problem with UNION's without braces and SQL_CALC_FOUND_ROWS, LIMIT #,# and ORDER BY...LIMIT
-
Sinisa@sinisa.nasamreza.org authored
Fix for SQL_CALC_FOUND_ROWS in UNION's
-
Sinisa@sinisa.nasamreza.org authored
Test case for the LEAST() bug in LEFT JOIN
-
Sinisa@sinisa.nasamreza.org authored
Fix for a bug with LEAST() in WHERE clause ha_innodb.cc: Fix for a configure bug multi_update.result, multi_update.test: Fix for the update with NULL's in the result set sql_update.cc: Fix for the update with NULL's in the result set Fix for the update with NULL's in the result set Fix for the update with NULL's in the result set
-
serg@serg.mylan authored
-
- 19 Aug, 2003 5 commits
-
-
dlenev@mysql.com authored
log-slave-updates since this causes unexpected values in Exec_master_log_pos in A->B->C replication setup, synchronization problems in master_pos_wait()... Still this brokes some functionality in sql/repl_failsafe.cc (but this file is not used now)
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
optimization: abort search for common (>50% rows) words earlier.
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-build
-
lenz@mysql.com authored
-