MySQL  8.0.27
Source Code Documentation
Binlog Event Header Flags

Macros

#define LOG_EVENT_THREAD_SPECIFIC_F   0x4
 If the query depends on the thread (for example: TEMPORARY TABLE). More...
 
#define LOG_EVENT_SUPPRESS_USE_F   0x8
 Suppress the generation of 'USE' statements before the actual statement. More...
 
#define LOG_EVENT_ARTIFICIAL_F   0x20
 Artificial events are created arbitarily and not written to binary log. More...
 
#define LOG_EVENT_RELAY_LOG_F   0x40
 Events with this flag set are created by slave IO thread and written to relay log. More...
 
#define LOG_EVENT_IGNORABLE_F   0x80
 For an event, 'e', carrying a type code, that a slave, 's', does not recognize, 's' will check 'e' for LOG_EVENT_IGNORABLE_F, and if the flag is set, then 'e' is ignored. More...
 
#define LOG_EVENT_NO_FILTER_F   0x100
 Events with this flag are not filtered (e.g. More...
 
#define LOG_EVENT_MTS_ISOLATE_F   0x200
 MTS: group of events can be marked to force its execution in isolation from any other Workers. More...
 

Detailed Description

Macro Definition Documentation

◆ LOG_EVENT_ARTIFICIAL_F

#define LOG_EVENT_ARTIFICIAL_F   0x20

Artificial events are created arbitarily and not written to binary log.

These events should not update the master log position when slave SQL thread executes them.

◆ LOG_EVENT_IGNORABLE_F

#define LOG_EVENT_IGNORABLE_F   0x80

For an event, 'e', carrying a type code, that a slave, 's', does not recognize, 's' will check 'e' for LOG_EVENT_IGNORABLE_F, and if the flag is set, then 'e' is ignored.

Otherwise, 's' acknowledges that it has found an unknown event in the relay log.

◆ LOG_EVENT_MTS_ISOLATE_F

#define LOG_EVENT_MTS_ISOLATE_F   0x200

MTS: group of events can be marked to force its execution in isolation from any other Workers.

So it's a marker for Coordinator to memorize and perform necessary operations in order to guarantee no interference from other Workers. The flag can be set ON only for an event that terminates its group. Typically that is done for a transaction that contains a query accessing more than OVER_MAX_DBS_IN_EVENT_MTS databases.

◆ LOG_EVENT_NO_FILTER_F

#define LOG_EVENT_NO_FILTER_F   0x100

Events with this flag are not filtered (e.g.

on the current database) and are always written to the binary log regardless of filters.

◆ LOG_EVENT_RELAY_LOG_F

#define LOG_EVENT_RELAY_LOG_F   0x40

Events with this flag set are created by slave IO thread and written to relay log.

◆ LOG_EVENT_SUPPRESS_USE_F

#define LOG_EVENT_SUPPRESS_USE_F   0x8

Suppress the generation of 'USE' statements before the actual statement.

This flag should be set for any events that does not need the current database set to function correctly. Most notable cases are 'CREATE DATABASE' and 'DROP DATABASE'.

This flags should only be used in exceptional circumstances, since it introduce a significant change in behaviour regarding the replication logic together with the flags –binlog-do-db and –replicated-do-db.

◆ LOG_EVENT_THREAD_SPECIFIC_F

#define LOG_EVENT_THREAD_SPECIFIC_F   0x4

If the query depends on the thread (for example: TEMPORARY TABLE).

Currently this is used by mysqlbinlog to know it must print SET @PSEUDO_THREAD_ID=xx; before the query (it would not hurt to print it for every query but this would be slow).