summaryrefslogtreecommitdiff
path: root/sql/slave.h
diff options
context:
space:
mode:
authorpetr@mysql.com <>2006-05-05 10:45:58 +0400
committerpetr@mysql.com <>2006-05-05 10:45:58 +0400
commitfec70c97c93537001bc51538221328a3d2dfa37e (patch)
treec388200837e23985854de7a23be71ad14804ceda /sql/slave.h
parent55ccf0fe87daf94c0c84c031ba9d6ff50c843ffb (diff)
downloadmariadb-git-fec70c97c93537001bc51538221328a3d2dfa37e.tar.gz
WL#3153 "Split logs". Recommit with post-review fixes
Diffstat (limited to 'sql/slave.h')
-rw-r--r--sql/slave.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/sql/slave.h b/sql/slave.h
index 0b77d7f7c4f..053358dc686 100644
--- a/sql/slave.h
+++ b/sql/slave.h
@@ -73,7 +73,7 @@
run_lock protects all information about the run state: slave_running, and the
existence of the I/O thread (to stop/start it, you need this mutex).
data_lock protects some moving members of the struct: counters (log name,
- position) and relay log (MYSQL_LOG object).
+ position) and relay log (MYSQL_BIN_LOG object).
In RELAY_LOG_INFO: run_lock, data_lock
see MASTER_INFO
@@ -81,7 +81,7 @@
Order of acquisition: if you want to have LOCK_active_mi and a run_lock, you
must acquire LOCK_active_mi first.
- In MYSQL_LOG: LOCK_log, LOCK_index of the binlog and the relay log
+ In MYSQL_BIN_LOG: LOCK_log, LOCK_index of the binlog and the relay log
LOCK_log: when you write to it. LOCK_index: when you create/delete a binlog
(so that you have to update the .index file).
*/