[MDEV-17312] BACKUP: track and report DDLs Created: 2018-09-27  Updated: 2019-03-04  Resolved: 2019-03-04

Status: Closed
Project: MariaDB Server
Component/s: Backup
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Sergei Golubchik Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-17308 BACKUP: mariabackup support Closed
Duplicate
is duplicated by MDEV-18465 Logging of DDL statements during backup Closed
Relates
relates to MDEV-5336 Implement BACKUP STAGE for safe exter... Closed

 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).

 Comments   
Comment by Vladislav Vaintroub [ 2018-09-27 ]

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.

Generated at Thu Feb 08 08:35:31 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.