Fix inaccurate lock description for backup.start in arch-cursor.dox

XMLWordPrintableJSON

    • Type: Documentation
    • Resolution: Fixed
    • Priority: Minor - P4
    • WT12.0.0, 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: Documentation
    • None
    • Storage Engines - Persistence
    • 935.371
    • SE Persistence backlog
    • None

      Summary

      The architecture documentation in src/docs/arch-cursor.dox (line 183) incorrectly states that WT_CONNECTION_IMPL->backup.start (formerly hot_backup_start) "can only be accessed when the connection schema lock is held." The field is actually guarded by backup.lock (the hot backup read-write lock), not the schema lock.

      Fix

      Update the sentence to reference backup.lock instead of the schema lock.

      Context

      Spotted during review of PR #13793 (WT-17531). The inaccuracy predates that PR and was not introduced by it.

            Assignee:
            Etienne Petrel
            Reporter:
            Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: