Fix wsrep_affected_rows.

The value of wsrep_affected_rows were not reseted properly for
slave. Now we also wsrep_affected_rows in Xid_log_event::do_apply_event
also , apart from THD::cleanup_after_query().

Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
This commit is contained in:
Sachin Setiya 2017-03-16 02:13:31 +05:30
commit 5bb7653667
4 changed files with 9 additions and 11 deletions

View file

@ -7422,6 +7422,10 @@ int Xid_log_event::do_apply_event(rpl_group_info *rgi)
Record any GTID in the same transaction, so slave state is transactionally
consistent.
*/
/*Set wsrep_affected_rows = 0 */
thd->wsrep_affected_rows= 0;
if (rgi->gtid_pending)
{
sub_id= rgi->gtid_sub_id;