Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
10.0.2
-
None
-
None
-
None
Description
We have the attached patch in our MySQL and MariaDB trees that removes the code putting stop events into binlog. The reasoning for removing these events is:
- The slave takes no action in response to the event so it isn't needed to begin with.
- If the master and slave are running with different binlog formats, the slave writes the stop event in its format while the rest of the events in the relay logs are of the master's format. This can cause the SQL thread to explode when it tries to read the stop event.
- If the master is generating an ID sequence we do not want the stop event to consume an ID.
Could you consider including this patch into MariaDB?