Better locking when using MVCC storage engines

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Concurrency, Storage
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This feature request is for the Storage Engine API.

      When the underlying engine provides MVCC, there is a lot that can be done to optimize locking in the higher levels. You don't need to lock on reads, since every read gets a consistent state of the database.

      Are you planning to optimize locking as part of pluggable storage engine API project?

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Igor Canadi
            Votes:
            1 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: