• Mats Kindahl's avatar
    Bug #44442: Incident events are silent in mysqlbinlog output · 8f95c5e1
    Mats Kindahl authored
          
    In the output from mysqlbinlog, incident log events were
    represented as just a comment. Since the incident log event
    represents an incident that could cause the contents of the
    database to change without being logged to the binary log,
    it means that if the SQL is applied to a server, it could
    potentially lead to that the databases are out of sync.
    
    In order to handle that, this patch adds the statement "RELOAD
    DATABASE" to the SQL output for the incident log event. This will
    require a DBA to edit the file and handle the case as apropriate
    before applying the output to a server.
    
    mysql-test/suite/binlog/t/binlog_incident-master.opt:
      Options file to cause server to generate an incident log
      event when executing a REPLACE.
    mysql-test/suite/binlog/t/binlog_incident.test:
      Test to check that the incident log event is represented
      correctly in the output from mysqlbinlog.
    sql/log_event.cc:
      The incident log event now ouput a "RELOAD DATABASE" instead
      of just a comment. RELOAD DATABASE is not an existing command
      and will generate a syntax error.
    8f95c5e1
binlog_incident.result 167 Bytes