Please sign in to comment.
BUG#12662190:COM_COMMIT IS NOT INCREMENTED FROM THE BINARY LOGS ON SL…
…AVE, COM_BEGIN IS PROBLEM: -------- When binary log statements are replayed on the slave, BEGIN is represented in com_counters but COMMIT is not. Similarly in 'ROW' based replication 'INSERT','UPDATE',and 'DELETE' com_counters are not getting incremented when the binary log statements are replayed at slave. ANALYSIS: --------- In 'ROW' based replication for COMMIT,INSERT,UPDATE and DELETE operations following special events are invoked. Xid_log_event,Write_rows_log_event,Update_rows_log_event,Update_rows_log_event. The above mentioned events doesn't go through the parser where the 'COM_COUNTERS' are incremented. FIX: ----- Increment statements are added at appropriate events. Respective functions are listed below. 'Xid_log_event::do_apply_event' 'Write_rows_log_event::do_before_row_operations' 'Update_rows_log_event::do_before_row_operations' 'Delete_rows_log_event::do_before_row_operations' --BZR-- revision-id: email@example.com property-branch-nick: Bug12662190 property-file-info: ld7:file_id65:sp1f-log_event.cc-19700101030959-msmqlflsngxosswid2hpzxly5vfqdddc7:message119:Added code to increment counts for 'COM_INSERT','COM_UPDATE', property-file-info: 'COM_DELETE' and 'COM_COMMIT'during ROW based replicaiton4:path16:sql/log_event.ccee testament3-sha1: 03a97ebea95b3d62ad79b50a08cc607f81cdb5ec
- Loading branch information...
Showing with 66 additions and 0 deletions.