Correctly handle unpublished tables with only unstable data

XMLWordPrintableJSON

    • Storage Engines, Storage Engines - Persistence
    • 0.001
    • None
    • None

      With the current WiredTiger logic, a newly created btree with just unstable data (and no stable data) is included in a checkpoint, which results in a (presumably) empty root page being written out and the checkpoint created. This violates the assumption that an unpublished table does not have any pages, and it also trips the check for having stable data in an unpublished table as a false positive.

            Assignee:
            Peter Macko
            Reporter:
            Peter Macko
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: