Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Fix Version/s: N/A
    • Component/s: Backup
    • Labels:
      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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: