Mysql undo

14.6.3.4 Undo Tablespaces

   Undo tablespaces contain undo logs, which are collections of undo log records that contain information about how to undo the latest change by a transaction to a clustered index record.Undo logs exist within undo log segments, which are contained within rollback segments. The innodb_rollback_segments variable defines the number of rollback segments allocated to each undo tablespace.

   回滚表空间包含回滚日志，回滚日志是回滚日志记录的集合，其中包含有关如何回滚事务对聚集索引记录的最新更改的信息。回滚日志存在于回滚日志段中，回滚日志段包含在回滚段中。innodb_rollback_segments变量定义分配给每个undo表空间的回滚段数。

 

   Undo logs can be stored in one or more undo tablespaces instead of the system tablespace. This layout differs from the default configuration in which undo logs reside in the system tablespace. The I/O patterns for undo logs make undo tablespaces good candidates for SSD storage, while keeping the system tablespace on hard disk storage.

   撤消日志可以存储在一个或多个撤消表空间中，而不是存储在系统表空间中。这种设计有别于回滚日志包含在系统表空间中的默认配置。undo日志的I/O模式使undo表空间很适合SSD存储，同时将系统表空间保留在硬盘存储上。

 

   The number of undo tablespaces used by InnoDB is controlled by the innodb_undo_tablespaces
configuration option. This option can only be configured when initializing the MySQL instance. It cannot
be changed afterward.

  InnoDB使用的undo表空间的数量由Innodb_undo_tablespaces配置选项控制。此选项只能在初始化MySQL实例时配置。以后不能更改。

 

Note
The innodb_undo_tablespaces configuration option is deprecated and will
be removed in a future release.

innodb_undo_tablespaces配置项已被废弃，将在高版本中移除。

 

Undo tablespaces and individual segments inside those tablespaces cannot be dropped. However,
undo logs stored in undo tablespaces can be truncated. For more information, see Truncating Undo
Tablespaces.

回滚表空间和这些表空间中的各个段是不能被删除的。但是，可以truncate存储在undo表空间中的undo日志。有关详细信息，请参见truncate undo表空间。

 

 

 

Configuring Undo Tablespaces

To configure undo tablespaces for a MySQL instance, perform the following steps. It is assumed that
you are performing the procedure on a test instance prior to deploying the configuration to a production
system.

要