Incremental backups may take up to 5x more space after the fix for bug #1022562

Reported by Alexey Kopytov on 2012-08-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
High
Laurynas Biveinis
2.0
High
Laurynas Biveinis
2.1
High
Laurynas Biveinis

Bug Description

Fix for bug #1022562 introduced a regression that may potentially lead to a 5x increase in disk space occupied by incremental backups.

The problem is that after the fix for bug #1022562 incremental backups take 64 KB more per _every_ table, even if it has not been modified. We have customers with 100,000+ tables (see bug #950334). A simple calculation shows their incremental backups would now take 6+ GB more, even if there have been absolutely no data updates.

I think the fix should be re-implemented to properly initialize the 1st page when a new tablespace has to be created on prepare. It's quite easy to do, we can reuse the code from fil_create_new_single_table_tablespace().

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers