Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-15528

Punch holes when pages are freed

    XMLWordPrintable

    Details

      Description

      When a InnoDB data file page is freed, its contents becomes garbage, and any storage allocated in the data file is wasted.

      We should introduce an InnoDB redo log record for marking pages as freed. This record, say, MLOG_PAGE_FREE, could be treated as no-op, or we could elect to punch a hole, especially when the page_compressed=1 option is used.

      If scrubbing is enabled, we should initialize the page with zeros. This should replace some of the non-working scrubbing logic (MDEV-8139).

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11696 Page Compression Has No Effect on Table Data File Size

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8139 Fix scrubbing

          • Major - Major loss of function.
          • Confirmed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12226 Avoid writes of freed (garbage) pages to InnoDB temporary tablespace

          • Major - Major loss of function.
          • Confirmed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16796 TRUNCATE TABLE slowdown with innodb_file_per_table=ON

          • Major - Major loss of function.
          • Closed

            Activity

              People

              • Assignee:
                thiru Thirunarayanan Balathandayuthapani
                Reporter:
                marko Marko Mäkelä
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: