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

BACKUP: track and report DDLs

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • N/A
    • Backup
    • None

    Description

      On BACKUP START the server should start monitoring DDLs and collect all names of tables that had their metadata changed.

      This can be collected in a temporary table (MEMORY with overflow to disk, as usual) and returned, for example, in a INFORMATION_SCHEMA table (preferrably with file names, if possible).

      The backup client can thus retrieve all such tables (that were supposedly created/dropped/renamed/modified during the backup process) and copy them again (or drop or rename in the backup — the I_S table should have enough information for that).

      Attachments

        Issue Links

          is blocked by

          Task - A task that needs to be done. MDEV-17308 BACKUP: mariabackup support

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is duplicated by

          Task - A task that needs to be done. MDEV-18465 Logging of DDL statements during backup

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-5336 Implement BACKUP STAGE for safe external backups

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

          Activity

            wlad Vladislav Vaintroub added a comment - - edited

            I think that it would be hard to do efficient renames in Aria, just based on file names and operations in the DDL log.
            Because the table can be recreated several times while backup is running, we can not know for sure which version of the table is now in the backup.
            With Innodb it is possible to know which version we have, because tablespaces have IDs that change if file is dropped and recreated.

            In absence of unique versioning, we'll have to re-copy new and renamed files that are in the DDL log.

            wlad Vladislav Vaintroub added a comment - - edited I think that it would be hard to do efficient renames in Aria, just based on file names and operations in the DDL log. Because the table can be recreated several times while backup is running, we can not know for sure which version of the table is now in the backup. With Innodb it is possible to know which version we have, because tablespaces have IDs that change if file is dropped and recreated. In absence of unique versioning, we'll have to re-copy new and renamed files that are in the DDL log.

            People

              Unassigned Unassigned
              serg Sergei Golubchik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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