Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
Backup through mysqldump loses historical data from versioned tables.
mysqldump does not read historical rows from the versioned tables, it runs SELECT, not SELECT .. FOR SYSTEM_TIME ALL. But even if we fixed it, it would still be impossible to load this data back, since we are dealing either with invisible columns into which we can't insert at all, or with virtual columns for which values are ignored. So, for now it becomes a known limitation which needs to be documented.
Attachments
Issue Links
- causes
-
MDEV-29730 mysqldump --dump-history creates broken dump if there are precision-versioned tables
- Closed
-
MDEV-29736 mysqldump sets system_versioning_insert_history=1 twice and doesn't restore previous value
- Closed
-
MDEV-29737 mysqldump doesn't check for --tz-utc when it accepts --dump-history
- Closed
-
MDEV-29828 Indicate that --dump-history only applies to timestamp-based versioning
- Closed
- duplicates
-
MDEV-23125 Backfilling System Versioned Tables
- Closed
- includes
-
MDEV-16733 mysqldump --tab and --xml options are conflicting
- Closed
-
MDEV-16734 LOAD DATA and system_versioning_modify_history
- Closed
- is blocked by
-
MDEV-15923 option to control who can set session @@timestamp
- Closed
-
MDEV-16546 System versioning setting to allow history modification
- Closed
-
MDEV-16684 Wrong timestamps on restore from mysqldump --compact
- Closed
- is duplicated by
-
MDEV-16798 need mysqldump option to include SYSTEM VERSIONING historical records in backups
- Closed
- is part of
-
MDEV-29547 prepare 10.11.0 preview releases
- Closed
- relates to
-
MDEV-16355 Add option for mysqldump to read data as of specific timestamp from system-versioned tables
- Closed
-
MDEV-16766 mysqldump: dump history in XML
- Open
-
MDEV-29741 SHOW BINLOG EVENTS shows garbage with system_versioning_insert_history=on
- Closed
-
MDEV-29750 Triggers can modify history
- Closed