← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to drizzled/slave.h

  • Committer: Grant Limberg
  • Date: 2008-08-12 21:13:01 UTC
  • mto: (322.1.1 codestyle)
  • mto: This revision was merged to the branch mainline in revision 324.
  • Revision ID: grant@glsoftware.net-20080812211301-ym3wsowelkgp16s2
renamed all instances of MYSQL_ to DRIZZLE_

Show diffs side-by-side

added added

removed removed

Lines of Context:
drizzled/slave.h
93
93
  run_lock protects all information about the run state: slave_running, thd
94
94
  and the existence of the I/O thread to stop/start it, you need this mutex).
95
95
  data_lock protects some moving members of the struct: counters (log name,
96
 
  position) and relay log (MYSQL_BIN_LOG object).
 
96
  position) and relay log (DRIZZLE_BIN_LOG object).
97
97
 
98
98
  In Relay_log_info: run_lock, data_lock
99
99
  see Master_info
101
101
  Order of acquisition: if you want to have LOCK_active_mi and a run_lock, you
102
102
  must acquire LOCK_active_mi first.
103
103
 
104
 
  In MYSQL_BIN_LOG: LOCK_log, LOCK_index of the binlog and the relay log
 
104
  In DRIZZLE_BIN_LOG: LOCK_log, LOCK_index of the binlog and the relay log
105
105
  LOCK_log: when you write to it. LOCK_index: when you create/delete a binlog
106
106
  (so that you have to update the .index file).
107
107
*/
128
128
  I started with using an enum, but
129
129
  enum_variable=1; is not legal so would have required many line changes.
130
130
*/
131
 
#define MYSQL_SLAVE_NOT_RUN         0
132
 
#define MYSQL_SLAVE_RUN_NOT_CONNECT 1
133
 
#define MYSQL_SLAVE_RUN_CONNECT     2
 
131
#define DRIZZLE_SLAVE_NOT_RUN         0
 
132
#define DRIZZLE_SLAVE_RUN_NOT_CONNECT 1
 
133
#define DRIZZLE_SLAVE_RUN_CONNECT     2
134
134
 
135
135
#define RPL_LOG_NAME (rli->group_master_log_name[0] ? rli->group_master_log_name :\
136
136
 "FIRST")