ThinkerQAQ

InnoDB

Databases · 9 notes

  1. 1.29 InnoDB Buffer Poolhistorical

    How InnoDB caches data and index pages, tracks free/dirty/cached pages, evicts cold pages, and decouples logical writes from data-file flushing.

  2. 1.30 InnoDB MVCChistorical

    How InnoDB uses transaction IDs, undo-based row versions, and Read Views so readers can observe consistent historical versions without blocking writers.

  3. 1.31 InnoDB Redo Loghistorical

    InnoDB write-ahead logging, redo buffering, fsync policy, group commit, crash recovery, and the relationship between redo log and binlog.

  4. 1.32 InnoDB Undo Loghistorical

    How undo records support transaction rollback and MVCC version reconstruction, and why long transactions delay undo purge.

  5. 1.33 InnoDB Transactionshistorical

    InnoDB transaction boundaries, ACID mechanisms, isolation levels, consistent reads, locking reads, MVCC, redo, and undo.

  6. InnoDB Tablespaceshistorical

    Logical and physical storage of InnoDB pages across system, file-per-table, undo, and temporary tablespaces.

  7. InnoDB vs. MyISAM Indexeshistorical

    How InnoDB clustered indexes differ from MyISAM's separate data and index storage.

  8. InnoDB Overviewhistorical

    Transactional MySQL storage with clustered indexes, MVCC, redo/undo, locking, and buffer-pool caching.

  9. InnoDB Flushinghistorical

    Writing dirty buffer-pool pages and redo state to durable storage under checkpoints and background pressure.