An error occurred fetching the project authors.
- 21 Dec, 2003 1 commit
-
-
konstantin@oak.local authored
see comments to the method why
-
- 19 Dec, 2003 2 commits
-
-
konstantin@oak.local authored
-
konstantin@oak.local authored
All tests pass (client_test included)
-
- 17 Dec, 2003 1 commit
-
-
guilhem@mysql.com authored
release the mutex before exiting the function, or it will be kept forever (=> START SLAVE, STOP SLAVE, etc will hang).
-
- 08 Dec, 2003 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
to mysqld that is executed for all new connections. (Similar to the client command: mysql_options(... MYSQL_INIT_COMMAND ...).
-
- 04 Dec, 2003 2 commits
-
-
guilhem@mysql.com authored
we change THD::system_thread from a 'bool' to a bitmap to be able to distinguish between delayed-insert threads and slave threads. - Fix for BUG#1701 "Update from multiple tables" (one line in sql_parse.cc, plus a new test rpl_multi_update.test). That's just adding an initialization.
-
guilhem@mysql.com authored
The problem was that when the slave SQL thread reads a hot relay log (hot = the one being written to by the slave I/O thread), it must have the LOCK_log. It already took it for read_log_event(), but needs it also for check_binlog_magic(). This should fix all recently reported failures of the rpl_max_relay_size test in 4.1 and 5.0 (though the bug exists since 4.0, it showed up first in 5.0).
-
- 28 Nov, 2003 1 commit
-
-
guilhem@mysql.com authored
the relay log before flushing master.info. Doing 'before' leads to duplicate event, doing after leads to missing event. Both can be as destructive, but 'duplicate' enables us to later add detection code to catch it. Whereas 'missing' can't be caught (it can't, because the I/O thread can produce legal position jumps, for example if it has ignored an event coming from this slave (rememember that starting from 4.1.1, the I/O thread filters the server id).
-
- 23 Nov, 2003 1 commit
-
-
guilhem@gbichot2 authored
Now the I/O thread (in flush_master_info()) flushes the relay log to disk after reading every event. Slower but provides additionnal safety in case of brutal crash. I had to make the flush optional (i.e. add a if(some_bool_argument) in the function) because sometimes flush_master_info() is called when there is no usable relay log (the relay log's IO_CACHE is not initialized so can't be flushed).
-
- 22 Nov, 2003 1 commit
-
-
monty@mysql.com authored
Don't flush cur_log (relay log) on flush_relay_log_info becasue this crashes the server if cur_log is 'hot' and the io_thread has changed log file. Updated project files for windows Made rpl_change_master.test portable Ensure that mutex are not freed if not initilized
-
- 21 Nov, 2003 1 commit
-
-
paul@teton.kitebird.com authored
to order used in START SLAVE syntax.
-
- 20 Nov, 2003 1 commit
-
-
paul@ice.snake.net authored
(Initial caps for each word.) For example, instead of writing Until_condition, Until_Log_File, and Until_log_pos, write Until_Condition, Until_Log_File, and Until_Log_pos.
-
- 03 Nov, 2003 1 commit
-
-
guilhem@mysql.com authored
rli->save_temporary_tables and slave_open_temp_tables (in old 4.0 you could make "SHOW STATUS LIKE 'slave_open_temp_tables'" grow indefinitely by doing RESET SLAVE and replicating always the same CREATE TEMPORARY TABLE). It's critical to reset save_temporary_tables to 0 (otherwise you may later read memory which has been freed) so this changeset should go into 4.1.
-
- 31 Oct, 2003 1 commit
-
-
guilhem@mysql.com authored
- when we don't have in_addr_t, use uint32. - a forgotten initialization of slave_proxy_id in sql/log_event.cc (was not really "forgot", was "we needn't init it there", but there was one case where we needed...). - made slave_proxy_id always meaningful in THD and Log_event, so we can rely more on it (no need to test if it's meaningful). THD::slave_proxy_id is equal to THD::thread_id except for the slave SQL thread. - clean up the slave's temporary table (i.e. free their memory) when slave server shuts down.
-
- 29 Oct, 2003 1 commit
-
-
guilhem@mysql.com authored
"If 2 master threads with same-name temp table, slave makes bad binlog" and (two birds with one stone) for BUG#1240 "slave of slave breaks when STOP SLAVE was issud on parent slave and temp tables". Here is the design change: in a slave running with --log-slave-updates, events are now logged with the thread id they had on the master. So no more id conflicts between master threads, but introduces id conflicts between one master thread and one normal client thread connected to the slave. This is solved by storing the server id in the temp table's name. New test which requires mysql-test-run to be run with --manager, otherwise it will be skipped. Undoing a Monty's change (hum, a chill runs down my spine ;) which was "Cleanup temporary tables when slave ends" in ChangeSet 1.1572.1.1.
-
- 16 Oct, 2003 1 commit
-
-
guilhem@mysql.com authored
while the slave is connected.
-
- 15 Oct, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Fixed chsize() problem on windows Extend default timeout on windows clients to 1 year (to avoid timeout problems)
-
- 11 Oct, 2003 1 commit
-
-
serg@serg.mylan authored
-
- 09 Oct, 2003 1 commit
-
-
guilhem@mysql.com authored
a Format_description_log_event (or maybe it will be named Description_log_event) which is not recognized by 4.0, so a 4.0 can't be a slave of 5.0. We detect it early to produce a helpful message instead of "corrupted relay log" later.
-
- 08 Oct, 2003 2 commits
-
-
guilhem@gbichot2 authored
"Add a column "Timestamp_of_last_master_event_executed" in SHOW SLAVE STATUS". Finally this is adding - Slave_IO_State (a copy of the State column of SHOW PROCESSLIST for the I/O thread, so that the users, most of the time, has enough info with only SHOW SLAVE STATUS). - Seconds_behind_master. When the slave connects to the master it does SELECT UNIX_TIMESTAMP() on the master, computes the absolute difference between the master's and the slave's clock. It records the timestamp of the last event executed by the SQL thread, and does a small computation to find the number of seconds by which the slave is late.
-
monty@narttu.mysql.fi authored
-
- 19 Sep, 2003 1 commit
-
-
hf@deer.(none) authored
embedded library hash_insert renamed to my_hash_insert to avoid name intersection with another libraries is there better idea?
-
- 13 Sep, 2003 1 commit
-
-
dlenev@dlenev.mshome authored
-
- 12 Sep, 2003 1 commit
-
-
guilhem@mysql.com authored
DO NOT COPY THIS CODE TO 4.0. The bugfix is better in 4.0, but here in 3.23 we don't want to add a new error code so we just use ER_EMPTY_QUERY. Bug was: "If a query was ignored on the slave (because of @code{replicate-ignore-table} and other similar rules), the slave still checked if the query got the same error code (0, no error) as on the master. So if the master had an error on the query (for example, ``Duplicate entry'' in a multiple-row insert), then the slave stopped and warned that the error codes didn't match. (Bug #797)"
-
- 11 Sep, 2003 2 commits
-
-
guilhem@mysql.com authored
Now LOAD DATA FROM MASTER does not drop the database, instead it only tries to create it, and drops/creates table-by-table. * replicate_wild_ignore_table='db1.%' is now considered as "ignore the 'db1' database as a whole", as it already works for CREATE DATABASE and DROP DATABASE.
-
monty@mashka.mysql.fi authored
Note that mix_innodb_myisam_binlog and union fails after this patch (Will be fixed shortly by maintaners of this code)
-
- 03 Sep, 2003 1 commit
-
-
kostja@oak.local authored
-
- 01 Sep, 2003 1 commit
-
-
dlenev@dlenev.mshome authored
Added proper options to CHANGE MASTER TO, new fields to SHOW SLAVE STATUS, Honoring this parameters during connection to master. Introduced new format of master.info file
-
- 27 Aug, 2003 1 commit
-
-
monty@narttu.mysql.fi authored
-
- 25 Aug, 2003 2 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
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".
-
- 23 Aug, 2003 2 commits
-
-
guilhem@mysql.com authored
OPTION_BIG_SELECTS.
-
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.
-
- 21 Aug, 2003 1 commit
-
-
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 1 commit
-
-
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.
-
- 19 Aug, 2003 2 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)
-
monty@mashka.mysql.fi authored
-
- 18 Aug, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Use server character set if --default-character-set is not used Added convert_string() for more efficient alloc+character-set convert of strings
-
- 07 Aug, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
(Mostly code cleanups)
-
- 04 Aug, 2003 1 commit
-
-
guilhem@mysql.com authored
- Bug #985: "Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong." Now RESET SLAVE puts correct info in mi->host etc. A new test rpl_reset_slave for that. - Bug #986: "CHANGE MASTER & START SLAVE do not reset error columns in SHOW SLAVE STATUS". Now these reset the errors.
-