mariadb/storage/innobase/trx
Marko Mäkelä 4bfdba2e89 MDEV-26672 innodb_undo_log_truncate may reset transaction ID sequence
trx_rseg_header_create(): Add a parameter for the value that is
to be written to TRX_RSEG_MAX_TRX_ID. If we omit this write, then
the updated test innodb.undo_truncate will fail for the 4k, 8k, 16k
page sizes. This was broken ever since
commit 947efe17ed (MDEV-15158)
removed the writes of transaction identifiers to the TRX_SYS page.

srv_do_purge(): Truncate undo tablespaces also during slow shutdown
(innodb_fast_shutdown=0).

Thanks to Krunal Bauskar for noticing this problem.
2021-09-24 11:23:37 +03:00
..
trx0i_s.cc Merge 10.2 into 10.3 2021-07-27 10:47:17 +03:00
trx0purge.cc MDEV-26672 innodb_undo_log_truncate may reset transaction ID sequence 2021-09-24 11:23:37 +03:00
trx0rec.cc MDEV-25979 Invalid page number written to DB_ROLL_PTR 2021-06-21 18:13:28 +03:00
trx0roll.cc Merge 10.2 into 10.3 2021-07-27 10:47:17 +03:00
trx0rseg.cc MDEV-26672 innodb_undo_log_truncate may reset transaction ID sequence 2021-09-24 11:23:37 +03:00
trx0sys.cc MDEV-26672 innodb_undo_log_truncate may reset transaction ID sequence 2021-09-24 11:23:37 +03:00
trx0trx.cc Merge 10.2 into 10.3 2021-07-27 10:47:17 +03:00
trx0undo.cc MDEV-25981 InnoDB upgrade fails 2021-06-22 09:30:25 +03:00