-
Magnus Blåudd authored
- The new Previous_gtids event in the binlog causes show_binlog_using_name.in to show the wrong event. - Replace usage of show_binlog_using_name.inc with show_binlog_event.inc since tha latter will automatically skip over the Previous_gtids event unless told not to do so. - There are still two tests using show_binlog_using_name.inc and those should be converted as well, but they are untfortunatley disabled so that task has to be deferred to later. - Also add suppression of the expected warning which the ndbcluster binlog injector writes to the error log when it starts up after mysqld restart. Same suppression already exist in ndb_rpl_gap_event.test
Magnus Blåudd authored- The new Previous_gtids event in the binlog causes show_binlog_using_name.in to show the wrong event. - Replace usage of show_binlog_using_name.inc with show_binlog_event.inc since tha latter will automatically skip over the Previous_gtids event unless told not to do so. - There are still two tests using show_binlog_using_name.inc and those should be converted as well, but they are untfortunatley disabled so that task has to be deferred to later. - Also add suppression of the expected warning which the ndbcluster binlog injector writes to the error log when it starts up after mysqld restart. Same suppression already exist in ndb_rpl_gap_event.test
Loading