Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
When slave_skip_errors has a setting, its useful to know which events got triggered.
Is a slave_skip_errors_binlog possible to store events in blog format that for the slave_skip_errors criteria are skipped?
This would assist with post-mortem, what when wrong as well as provide a recovery mechanism.