[MDEV-21132] Remove buf_page_t::newest_modification Created: 2019-11-23  Updated: 2022-06-09  Resolved: 2019-11-25

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.5.0

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

Issue Links:
Relates
relates to MDEV-28779 ALTER TABLE IMPORT TABLESPACE fails w... Closed
relates to MDEV-16526 Overhaul the InnoDB page flushing Closed

 Description   

At each mini-transaction commit, the log sequence number of the mini-transaction must be written to each modified page, so that it will be available in the FIL_PAGE_LSN field when the page is being read in crash recovery.

InnoDB was unnecessarily allocating redundant storage for the field, in buf_page_t::newest_modification. Let us access FIL_PAGE_LSN directly.

Furthermore, on ALTER TABLE…IMPORT TABLESPACE, we should write FIL_PAGE_LSN as 0 instead of using the value of log_sys.lsn at the start of the operation.


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