Review WT_CONNECTION.set_timestamp calls

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • v8.0
    • Repl 2024-03-18, Repl 2024-04-01, Repl 2024-04-15, Repl 2024-04-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In WT-12345, we no longer want set_timestamp to ignore calls that are trying to set timestamps backwards in time if force is not set.

      There are currently two calls to that function in wiredtiger_kv_engine.cpp:

      We understand that this API can be difficult for applications to use "correctly" in that way, since they can have multiple threads updating the WiredTiger timestamps, and we don't want an API that forces those threads to coordinate if it's not necessary for correctness. Therefore, it would be great to investigate if this happens in the two code paths I have linked above.

              Assignee:
              Samyukta Lanka
              Reporter:
              Etienne Petrel
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: