[MDEV-15529] IMPORT TABLESPACE unnecessarily uses the doublewrite buffer Created: 2018-03-09  Updated: 2018-03-10  Resolved: 2018-03-10

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0, 10.1, 10.2, 10.3
Fix Version/s: 10.2.14, 10.3.6

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: performance

Issue Links:
Relates
relates to MDEV-15527 page_compressed compressed page parti... Closed

 Description   

The purpose of the InnoDB doublewrite buffer is to make redo-logged write operations crash-safe. If InnoDB is killed in the middle of a page write, the redo log based recovery on subsequent InnoDB startup would detect the corrupted page.

The initial phase of ALTER TABLE…IMPORT TABLESPACE operation is not redo-logged or crash-safe, and it cannot possibly benefit from the doublewrite buffer. We should skip the doublewrite buffer in this case.

Note: This will cause page_compressed tables to expand during IMPORT TABLESPACE until MDEV-15527 has been fixed.


Generated at Thu Feb 08 08:22:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.