Reading fast truncated pages in a readonly database can lead to cache stuck

XMLWordPrintableJSON

    • None
    • None

      The table having fast truncated pages from a previous session and reading them in a read-only database environment can lead to cache stuck as the instantiated deleted pages cannot evict until the truncate operation is globally visible.

      1. Create a table and insert 10000 keys
      2. Close and open the database.
      3. Perform truncate operation, this will do a fast truncate.
      4. Reopen the database in a read-only environment.
      5. Read the key values before the truncate command. This operation fails as the cache gets full with all the instantiated deleted pages.

        1. test_truncate_readonly.py
          8 kB

              Assignee:
              Haribabu Kommi
              Reporter:
              Haribabu Kommi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: