mariadb/mysql-test/suite/mariabackup/apply-log-only.result

call mtr.add_suppression("InnoDB: New log files created");
CREATE TABLE t(a varchar(60)) ENGINE INNODB;
start transaction;
INSERT INTO t VALUES(1);
NOT FOUND /Rollback of trx with id/ in current_test
# expect NOT FOUND
SELECT count(*) FROM t;
count(*)
1
DROP TABLE t;
MDEV-13807 mariabackup --apply-log-only does generate redo log by performing rollback and possibly other tasks Skip rollback and other redo-log-generating tasks if srv_apply_log_only is set. Instead of assigning the debug variable recv_no_log_write = FALSE, assign it to srv_apply_log_only, so that any unwanted writes are caught. 2017-09-16 09:53:29 +03:00			`call mtr.add_suppression("InnoDB: New log files created");`
			`CREATE TABLE t(a varchar(60)) ENGINE INNODB;`
			`start transaction;`
			`INSERT INTO t VALUES(1);`
			`NOT FOUND /Rollback of trx with id/ in current_test`
			`# expect NOT FOUND`
			`SELECT count(*) FROM t;`
			`count(*)`
			`1`
			`DROP TABLE t;`