mariadb/mysql-test/suite/mariabackup/undo_space_id.result

# Create 2 UNDO TABLESPACE(UNDO001(space_id =3), UNDO002(space_id =4))
CREATE TABLE t1(a varchar(60)) ENGINE INNODB;
start transaction;
INSERT INTO t1 VALUES(1);
# xtrabackup backup
# Display undo log files from target directory
undo001
undo002
# xtrabackup prepare
# Display undo log files from targer directory
undo001
undo002
DROP TABLE t1;
#
#  MDEV-33980  mariadb-backup --backup is missing
#       retry logic for undo tablespaces
#
# xtrabackup backup
# Display undo log files from target directory
FOUND 5 /Retrying to read undo tablespace*/ in backup.log
MDEV-21216 InnoDB does dirty read of TRX_SYS page before recovery InnoDB startup was discovering undo tablespaces in a dirty way. It was reading a possibly stale copy of the TRX_SYS page before processing any redo log records. srv_start(): Do not call buf_pool_invalidate(). Invoke trx_rseg_get_n_undo_tablespaces() after the recovery has been initiated. recv_recovery_from_checkpoint_start(): Assert that the buffer pool is empty. This used to be guaranteed by the buf_pool_invalidate() call. trx_rseg_get_n_undo_tablespaces(): Move to the calling compilation unit, and reimplement in a simpler way. srv_undo_tablespace_create(): Remove the constant parameter size=SRV_UNDO_TABLESPACE_SIZE_IN_PAGES. srv_undo_tablespace_open(): Reimplement in a cleaner way, with more robust error handling. srv_all_undo_tablespaces_open(): Split from srv_undo_tablespaces_init(). srv_undo_tablespaces_init(): Read all "undo001","undo002" tablespace files directly, without consulting the TRX_SYS page via calling trx_rseg_get_n_undo_tablespaces(). This is joint work with Thirunarayanan Balathandayuthapani. 2019-12-04 15:00:57 +02:00			`# Create 2 UNDO TABLESPACE(UNDO001(space_id =3), UNDO002(space_id =4))`
MDEV-13561 Mariabackup is incompatible with retroactively created innodb_undo_tablespaces - Mariabackup supports starting undo tablespace id which is greater than 1. 2018-03-22 14:19:16 +05:30			`CREATE TABLE t1(a varchar(60)) ENGINE INNODB;`
			`start transaction;`
			`INSERT INTO t1 VALUES(1);`
			`# xtrabackup backup`
			`# Display undo log files from target directory`
MDEV-21216 InnoDB does dirty read of TRX_SYS page before recovery InnoDB startup was discovering undo tablespaces in a dirty way. It was reading a possibly stale copy of the TRX_SYS page before processing any redo log records. srv_start(): Do not call buf_pool_invalidate(). Invoke trx_rseg_get_n_undo_tablespaces() after the recovery has been initiated. recv_recovery_from_checkpoint_start(): Assert that the buffer pool is empty. This used to be guaranteed by the buf_pool_invalidate() call. trx_rseg_get_n_undo_tablespaces(): Move to the calling compilation unit, and reimplement in a simpler way. srv_undo_tablespace_create(): Remove the constant parameter size=SRV_UNDO_TABLESPACE_SIZE_IN_PAGES. srv_undo_tablespace_open(): Reimplement in a cleaner way, with more robust error handling. srv_all_undo_tablespaces_open(): Split from srv_undo_tablespaces_init(). srv_undo_tablespaces_init(): Read all "undo001","undo002" tablespace files directly, without consulting the TRX_SYS page via calling trx_rseg_get_n_undo_tablespaces(). This is joint work with Thirunarayanan Balathandayuthapani. 2019-12-04 15:00:57 +02:00			`undo001`
			`undo002`
MDEV-13561 Mariabackup is incompatible with retroactively created innodb_undo_tablespaces - Mariabackup supports starting undo tablespace id which is greater than 1. 2018-03-22 14:19:16 +05:30			`# xtrabackup prepare`
			`# Display undo log files from targer directory`
MDEV-21216 InnoDB does dirty read of TRX_SYS page before recovery InnoDB startup was discovering undo tablespaces in a dirty way. It was reading a possibly stale copy of the TRX_SYS page before processing any redo log records. srv_start(): Do not call buf_pool_invalidate(). Invoke trx_rseg_get_n_undo_tablespaces() after the recovery has been initiated. recv_recovery_from_checkpoint_start(): Assert that the buffer pool is empty. This used to be guaranteed by the buf_pool_invalidate() call. trx_rseg_get_n_undo_tablespaces(): Move to the calling compilation unit, and reimplement in a simpler way. srv_undo_tablespace_create(): Remove the constant parameter size=SRV_UNDO_TABLESPACE_SIZE_IN_PAGES. srv_undo_tablespace_open(): Reimplement in a cleaner way, with more robust error handling. srv_all_undo_tablespaces_open(): Split from srv_undo_tablespaces_init(). srv_undo_tablespaces_init(): Read all "undo001","undo002" tablespace files directly, without consulting the TRX_SYS page via calling trx_rseg_get_n_undo_tablespaces(). This is joint work with Thirunarayanan Balathandayuthapani. 2019-12-04 15:00:57 +02:00			`undo001`
			`undo002`
MDEV-13561 Mariabackup is incompatible with retroactively created innodb_undo_tablespaces - Mariabackup supports starting undo tablespace id which is greater than 1. 2018-03-22 14:19:16 +05:30			`DROP TABLE t1;`
MDEV-33980 mariadb-backup --backup is missing retry logic for undo tablespaces Problem: ======== - Currently mariabackup have to reread the pages in case they are modified by server concurrently. But while reading the undo tablespace, mariabackup failed to do reread the page in case of error. Fix: === Mariabackup --backup functionality should have retry logic while reading the undo tablespaces. 2024-04-30 14:16:08 +05:30			`#`
			`# MDEV-33980 mariadb-backup --backup is missing`
			`# retry logic for undo tablespaces`
			`#`
			`# xtrabackup backup`
			`# Display undo log files from target directory`
			`FOUND 5 /Retrying to read undo tablespace*/ in backup.log`