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 /Rolled back recovered transaction/ 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);`
MDEV-15143 InnoDB: Rollback of trx with id 0 completed When InnoDB has completed the rollback of a recovered transaction, it used to display the transaction identifier. This was broken in MySQL 5.7.2 in https://github.com/mysql/mysql-server/commit/2f5f3cd3ac46d46c7635e778b338f63b5521cd46 which was merged to MariaDB 10.2.2 in commit 2e814d4702d71a04388386a9f591d14a35980bfe. trx_rollback_active(): Cache the transaction ID before it will be reset by transaction commit. Do not display the message if the rollback was interrupted by shutdown (MDEV-13797, MDEV-12352). 2018-01-31 12:01:35 +02:00			`NOT FOUND /Rolled back recovered transaction/ in current_test`
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			`# expect NOT FOUND`
			`SELECT count(*) FROM t;`
			`count(*)`
			`1`
			`DROP TABLE t;`