diff options
| author | unknown <guilhem@mysql.com> | 2004-06-10 14:03:25 +0200 |
|---|---|---|
| committer | unknown <guilhem@mysql.com> | 2004-06-10 14:03:25 +0200 |
| commit | 0e6b9457fe40808e096df13e1388360caed5d9bf (patch) | |
| tree | f4e81a372e6e64ceba7b68702d875a0953aec067 /sql/repl_failsafe.cc | |
| parent | 350ad5003e90c4129a69937afaf7d87b828a506c (diff) | |
| download | mariadb-git-0e6b9457fe40808e096df13e1388360caed5d9bf.tar.gz | |
don't need to tag the slave SQL thread as "bootstrap". It causes duplicate
error messages when a query goes wrong.
Note that from now on, if you run with --slave-skip-error=xx, then nothing will
be printed to the error log when the slave is having this error xx and
skipping it (but you don't care as you want to skip it).
sql/repl_failsafe.cc:
a comment about the use of thd->bootstrap in failsafe (unused code)
Diffstat (limited to 'sql/repl_failsafe.cc')
| -rw-r--r-- | sql/repl_failsafe.cc | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/sql/repl_failsafe.cc b/sql/repl_failsafe.cc index 2a5381ae478..4feb24f06b2 100644 --- a/sql/repl_failsafe.cc +++ b/sql/repl_failsafe.cc @@ -63,6 +63,11 @@ static Slave_log_event* find_slave_event(IO_CACHE* log, static int init_failsafe_rpl_thread(THD* thd) { DBUG_ENTER("init_failsafe_rpl_thread"); + /* + thd->bootstrap is to report errors barely to stderr; if this code is + enable again one day, one should check if bootstrap is still needed (maybe + this thread has no other error reporting method). + */ thd->system_thread = thd->bootstrap = 1; thd->host_or_ip= ""; thd->client_capabilities = 0; |