[MDEV-21727] Optimize redo logging for ROW_FORMAT=COMPRESSED Created: 2020-02-13  Updated: 2020-06-09

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.5
Fix Version/s: 10.5

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

Issue Links:
Problem/Incident
is caused by MDEV-12353 Efficient InnoDB redo log record format Closed
Relates
relates to MDEV-22367 Remove write support for ROW_FORMAT=C... Closed
relates to MDEV-22839 ROW_FORMAT=COMPRESSED vs PAGE_COMPRES... Open

 Description   

The physical log format introduced in MDEV-12353 would allow us to write much less log for ROW_FORMAT=COMPRESSED pages, even when pages are being recompressed. There are multiple issues, including at least the following:

  • page_zip_compress() is being logged as a full page image. We could emit WRITE and MEMMOVE records in many cases.
  • A single mini-transaction may first write some log to a page and then restart from the scratch, writing an INIT_PAGE for a page_zip_compress(). The preceding records for the page should not have been written in the first place.

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