Optimize for in-order, non-overlapping modifications

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.1, WT3.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines 2019-06-03, Storage Engines 2019-06-17, Storage Engines 2019-07-01, Storage Engines 2019-08-12
    • 8
    • v4.0

      We can simplify and improve efficiency of WT_CURSOR::modify operations and subsequent reads by requiring that WT_MODIFY arrays be supplied in offset order and be non-overlapping.

      We should further consider disallowing modifications past the end of a record to avoid code that NUL-pads records.

            Assignee:
            Keith Bostic (Inactive)
            Reporter:
            Michael Cahill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: