5 commits

Author	SHA1	Message	Date
serg@serg.mylan	34fdd54e07	post-merge fixes	2003-11-25 20:06:41 +01:00
monty@mysql.com	d87494c5ac	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	2003-11-22 03:21:40 +02:00
monty@mysql.com	d08945498e	Fixed memory leak with RAID tables ... Fixed tests for RAID tables Detect uninitialized mutexes on lock and destroy	2003-11-21 14:41:57 +02:00
monty@mysql.com	8aeb63dd3b	Update VC++ files ... Portability fixes After merge fixes	2003-11-21 01:53:01 +02:00
guilhem@mysql.com	8377acc7d1	Fix for BUG#1870 ... "CHANGE MASTER makes SQL thread restart from coordinates of I/O thread". So, in CHANGE MASTER: when it seems reasonable that the user did not want to discontinue its replication (i.e. when he is not specifying host or port or master_log_file or master_log_pos; this will be documented), set the coordinates of the I/O thread to those of the SQL thread. This way, the SQL thread will see no discontinuity in the relay log (i.e. will skip no events), because the I/O thread will fill the brand new relay log with the events which are just after the position where the SQL thread had stopped (before CHANGE MASTER was issued). And a new test for this bug.	2003-11-18 17:31:17 +01:00