in-page-logging · research · also IPL

In-page logging

In-page logging stores database page updates as log records beside an unchanged page in the same flash erase block.

Related Observatory article: In-page logging on hesela.com

Reads replay the page's logs; a full log area triggers a merge into a clean block. The 2007 recovery extension forces relevant log sectors at commit and excludes uncommitted updates from merging. No-force refers to data pages, not an absence of durable log writes. [1]

Transactional IPL later adds snapshot-aware merging and alternative commit protocols with different recovery costs. [2]

Relations

related
Page-differential logging, Physiological logging, NAND erase block, Write-ahead log

Citations

  1. Lee and Moon. Design of Flash-Based DBMS: An In-Page Logging Approach. SIGMOD 2007, pp. 55-66, sections 3 and 5. (accessed 2026-11-13)
  2. Lee and Moon. Transactional In-Page Logging for Multiversion Read Consistency and Recovery. ICDE 2011, pp. 876-887, sections III-VI. (accessed 2026-11-13)

Further reading

  1. Hesela: log placement, commit and retained history (accessed 2026-11-13)
Sources & caveats
  • Historical research designs, not a feature claim for current SSDs. The IPL comparison is simulated; TIPL evaluates traced workloads. No hardware reproduction by Hesela.

JSON: /data/terms/in-page-logging.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. In-page logging. Hesela. 2026-11-13. https://hesela.dev/terms/in-page-logging/