Bug #47096 LOST_EVENTS incident not reported when --binlog-ignore-db is used

Description:
The LOST_EVENTS incident is not reported in binary logs when mysqld starts if the --binlog-ignore-db option is used.

How to repeat:
Using MySQL Cluster 7.0.7: start mysqld with --binlog-ignore-db=mysql (database is not important).
Stop the mysqld, start it again: and check the binary logs for LOST_EVENTS: not there.

Suggested fix:
LOST_EVENTS should be set no matter what option is set.

Also verified using MySQL Cluster 7.0bzr latest pull.

Same behavior is with --binlog-do-db also (tested on 7.0.9b and 7.0.10)

=== modified file 'sql/log.cc'
This patch fixes the problem:

--- sql/log.cc  2010-03-12 10:36:52 +0000
+++ sql/log.cc  2010-03-17 13:57:45 +0000
@@ -4278,6 +4278,7 @@ bool MYSQL_BIN_LOG::write(Log_event *eve
     */
     const char *local_db= event_info->get_db();
     if ((thd && !(thd->options & OPTION_BIN_LOG)) ||
+        (local_db) &&
        (!binlog_filter->db_ok(local_db)))
     {
       VOID(pthread_mutex_unlock(&LOCK_log));

Test file

Attachment: rpl_ndb_gap_event.test (application/octet-stream, text), 702 bytes.

Result file

Attachment: rpl_ndb_gap_event.result (application/octet-stream, text), 623 bytes.

Patch file

Attachment: rpl_ndb_gap_event.patch (text/x-diff), 409 bytes.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/104230

3169 Martin Skold	2010-03-24
      Bug#47096  LOST_EVENTS incident not reported when --binlog-ignore-db is used: Skip filtering on database for Incident_bilog_event
      added:
        mysql-test/suite/rpl_ndb/r/rpl_ndb_gap_event.result
        mysql-test/suite/rpl_ndb/t/rpl_ndb_gap_event-master.opt
        mysql-test/suite/rpl_ndb/t/rpl_ndb_gap_event.test
      modified:
        sql/log.cc
        sql/log_event.h

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/104235

3476 Martin Skold	2010-03-24 [merge]
      Merge
      added:
        mysql-test/suite/rpl_ndb/r/rpl_ndb_gap_event.result
        mysql-test/suite/rpl_ndb/t/rpl_ndb_gap_event-master.opt
        mysql-test/suite/rpl_ndb/t/rpl_ndb_gap_event.test
      modified:
        sql/log.cc
        sql/log_event.h

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/104242

3536 Martin Skold	2010-03-24 [merge]
      Merge
      added:
        mysql-test/suite/rpl_ndb/r/rpl_ndb_gap_event.result
        mysql-test/suite/rpl_ndb/t/rpl_ndb_gap_event-master.opt
        mysql-test/suite/rpl_ndb/t/rpl_ndb_gap_event.test
      modified:
        sql/log.cc
        sql/log_event.h

Documented bugfix in the NDB-6.3.33, 7.0.14, and 7.1.3 changelogs as follows:

      When mysqld was started with --binlog-do-db or --binlog-ignore-db, 
      no LOST_EVENTS incident was written to the binary log.

Closed.