[KongchangAI]
Concept重做日志

redo log

InnoDB's write-ahead log (WAL) that records all data modification operations. It is used during crash recovery to replay transactions that were committed but not yet flushed to disk, ensuring the durability property of ACID.

Timeline (last 90 days)

Oct 14

InnoDB's write path is log-first: any modification is first written to the redo log, then dirty pages are flushed asynchronously; after a crash, recovery is done by replaying redo, and rollback and multi-version reads are achieved through undo.

Unverified50%

All Facts (1)

Unverified

InnoDB's write path is log-first: any modification is first written to the redo log, then dirty pages are flushed asynchronously; after a crash, recovery is done by replaying redo, and rollback and multi-version reads are achieved through undo.

50%

Source Articles

Same Job, Two Engines: Comparing InnoDB and Iceberg InternalsOct 14