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

Provide "crash safe" options for CHECK TABLE and ALTER TABLE ... CHECK PARTITION ...

    XMLWordPrintable

    Details

      Description

      We need a safe way to run table checks for InnoDB tabes with statements like CHECK TABLE or ALTER TABLE ... CHECK PARTITION in production, that will NOT cause any deliberate assertion failures.

      Something like deprecated and removed since 10.3 innodb_corrupt_table_action option (the name may be different) for these statements (or all access) with values like "assert" (current behaviour), "warn" (add the details about corruption found and continue if possible or stop stating the table/partition is corrupted) etc. This should apply NOT only to page checksums, but to all other kinds of assertions we may hit in InnoDB in the process.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              valerii Valerii Kravchuk
              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.