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

Optimize redo logging for ROW_FORMAT=COMPRESSED

    XMLWordPrintable

Details

    Description

      The physical log format introduced in MDEV-12353 would allow us to write much less log for ROW_FORMAT=COMPRESSED pages, even when pages are being recompressed. There are multiple issues, including at least the following:

      • page_zip_compress() is being logged as a full page image. We could emit WRITE and MEMMOVE records in many cases.
      • A single mini-transaction may first write some log to a page and then restart from the scratch, writing an INIT_PAGE for a page_zip_compress(). The preceding records for the page should not have been written in the first place.

      Attachments

        Issue Links

          is caused by

          Task - A task that needs to be done. MDEV-12353 Efficient InnoDB redo log record format

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-22367 Remove write support for ROW_FORMAT=COMPRESSED

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-22839 ROW_FORMAT=COMPRESSED vs PAGE_COMPRESSION=1 - size comparison

          • Major - Major loss of function.
          • Open

          Activity

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.