Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-5127

Fix a bug where code uses leaf page size, not memory page max

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:

      Description

      The code in __wt_leaf_page_can_split uses maxleafpage to make a decision about whether a page is big. I believe it intends to use maxmempage instead.

      The maximum leaf page is likely to be 32k, wheras the maximum in-memory page is likely to be 10MB.

      The code was introduced in WT-2954, here is a link to the patch

      We should do some more spelunking through history before making this change, to ensure that it's a bug and not expected. If we determine that it's expected the comment should be update to be clearer.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-storage-engines Backlog - Storage Engines Team
            Reporter:
            alexander.gorrod Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: