mariadb/sql/rpl_constants.h

#ifndef RPL_CONSTANTS_H
#define RPL_CONSTANTS_H

/**
   Enumeration of the incidents that can occur for the server.
 */
enum Incident {
  /** No incident */
  INCIDENT_NONE = 0,

  /** There are possibly lost events in the replication stream */
  INCIDENT_LOST_EVENTS = 1,

  /** Shall be last event of the enumeration */
  INCIDENT_COUNT
};

#endif /* RPL_CONSTANTS_H */
WL#3464: Add replication event to denote gap in replication Adding an event that can be used to denote that an incident occured on the master. The event can be used to denote a gap in the replication stream, but can also be used to denote other incidents. In addition, the injector interface is extended with functions to generate an incident event. The function will also rotate the binary log after generating an incident event to get a fresh binary log. 2007-03-29 20:31:09 +02:00			`#ifndef RPL_CONSTANTS_H`
			`#define RPL_CONSTANTS_H`

			`/**`
			`Enumeration of the incidents that can occur for the server.`
			`*/`
			`enum Incident {`
			`/** No incident */`
BUG#40482: server/mysqlbinlog crashes when reading invalid Incident_log_event Problem: When an Incident_log_event contains a bad incident number on disk, the server crashes with an assertion. Fix: Don't validate input with assertions. Use errors. 2008-12-29 17:04:10 +01:00			`INCIDENT_NONE = 0,`
WL#3464: Add replication event to denote gap in replication Adding an event that can be used to denote that an incident occured on the master. The event can be used to denote a gap in the replication stream, but can also be used to denote other incidents. In addition, the injector interface is extended with functions to generate an incident event. The function will also rotate the binary log after generating an incident event to get a fresh binary log. 2007-03-29 20:31:09 +02:00
			`/** There are possibly lost events in the replication stream */`
BUG#40482: server/mysqlbinlog crashes when reading invalid Incident_log_event Problem: When an Incident_log_event contains a bad incident number on disk, the server crashes with an assertion. Fix: Don't validate input with assertions. Use errors. 2008-12-29 17:04:10 +01:00			`INCIDENT_LOST_EVENTS = 1,`
WL#3464: Add replication event to denote gap in replication Adding an event that can be used to denote that an incident occured on the master. The event can be used to denote a gap in the replication stream, but can also be used to denote other incidents. In addition, the injector interface is extended with functions to generate an incident event. The function will also rotate the binary log after generating an incident event to get a fresh binary log. 2007-03-29 20:31:09 +02:00
			`/** Shall be last event of the enumeration */`
			`INCIDENT_COUNT`
			`};`

			`#endif /* RPL_CONSTANTS_H */`