When a page is read into the BUFFER pool, buffered changes are merged upon completion of the read, before the page is made available.

Change buffer MERGING is performed as a background TASK. The innodb_io_capacity parameter sets an upper limit on the I/O activity performed by InnoDB background tasks such as merging data from the change buffer.

A change buffer merge is performed during crash recovery. Changes are applied from the change buffer (in the system tablespace) to leaf pages of secondary indexes as index pages are read into the buffer pool.

The change buffer is fully durable and will survive a system crash. Upon restart, change buffer merge operations RESUME as part of normal operations.

A full merge of the change buffer can be forced as part of a slow SERVER shutdown using --innodb-fast-shutdown=0.

When a page is read into the buffer pool, buffered changes are merged upon completion of the read, before the page is made available.

Change buffer merging is performed as a background task. The innodb_io_capacity parameter sets an upper limit on the I/O activity performed by InnoDB background tasks such as merging data from the change buffer.

A change buffer merge is performed during crash recovery. Changes are applied from the change buffer (in the system tablespace) to leaf pages of secondary indexes as index pages are read into the buffer pool.

The change buffer is fully durable and will survive a system crash. Upon restart, change buffer merge operations resume as part of normal operations.

A full merge of the change buffer can be forced as part of a slow server shutdown using --innodb-fast-shutdown=0.