Clarify usage of WT_PAGE_COMPRESSED flag in block_cache/block_io.c

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Block Cache
    • None
    • Storage Engines, Storage Engines - Persistence
    • SE Persistence backlog
    • None

      WT-15214 fixed the consistency issue with the WT_PAGE_ENCRYPTED flag.

      The objective of this ticket is to ensure the same consistency for the WT_PAGE_COMPRESSED flag. It should either always match the compressed state of the page (both in memory and on storage) or, if it doesn't, that behavior should be clearly documented.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Yury Ershov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: