Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
While dumping large database with --single-transaction option, there is a chance, that a table will be truncated during dump, resulting 'Table definition has changed, please retry transaction' error.
In some cases, it means that dumping database always fails, i.e. when a table, that gets often truncated, is dumped after a large table.
In environments, where changing database layout or backup strategy is not trivial, it makes using --single-transaction problematic.
The suggested --order-by-size option will dump tables according to their size, smaller tables first.
--order-by-size cannot be used when one is specifying table names on the command line.
Assuming, that truncated tables are usually small, dumping small tables first greatly reduces such errors.
Attachments
Issue Links
- relates to
-
MDEV-25571 mariadb-dump support for backup lock
-
- Open
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to MDEV-25571 [ MDEV-25571 ] |
| Summary | mysqldump order by size | mysqldump order by increasing size |
| Assignee | Daniel Black [ danblack ] | Michael Widenius [ monty ] |
| Summary | mysqldump order by increasing size | mysqldump --order-by-size |
| Description |
While dumping large database with --single-transaction option, there is a chance, that a table will be truncated during dump, resulting 'Table definition has changed, please retry transaction' error.
In some cases, it means that dumping database always fails, i.e. when a table, that gets often truncated, is dumped after a large table. In environments, where changing database layout or backup strategy is not trivial, it makes using --single-transaction problematic. Assuming, that truncated tables are usually small, dumping small tables first greatly reduces such errors. |
While dumping large database with --single-transaction option, there is a chance, that a table will be truncated during dump, resulting 'Table definition has changed, please retry transaction' error.
In some cases, it means that dumping database always fails, i.e. when a table, that gets often truncated, is dumped after a large table. In environments, where changing database layout or backup strategy is not trivial, it makes using --single-transaction problematic. The suggested --order-by-size option will dump tables according to their size, smaller tables first. --order-by-size cannot be used when one is specifying table names on the command line. Assuming, that truncated tables are usually small, dumping small tables first greatly reduces such errors. |
| issue.field.resolutiondate | 2022-04-13 10:11:53.0 | 2022-04-13 10:11:53.367 |
| Fix Version/s | 10.9.1 [ 27114 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
Pushed to 10.9 tree