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

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

      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.

            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            alexander.gorrod@mongodb.com Alexander Gorrod
            0 Vote for this issue
            4 Start watching this issue