lp://qastaging/~sergei.glushchenko/percona-xtrabackup/xb2.0-bug711166
- Get this branch:
- bzr branch lp://qastaging/~sergei.glushchenko/percona-xtrabackup/xb2.0-bug711166
Branch merges
Branch information
- Owner:
- Sergei Glushchenko
- Status:
- Development
Recent revisions
- 428. By Stewart Smith
-
merge fix for Bug #996493: innobackupex --apply-log doesn't read config from backup-my.cnf
- 427. By Alexey Kopytov
-
Bug #972169: --compress in 2.0 should be incompatible with --stream=tar
Bug #999750: incremental backups should be incompatible with
--stream=tarAs the 'tar' streaming format does not support compressed and
incremental backups, made the corresponding options incompatible with
--stream=tar. - 424. By Stewart Smith
-
Merge Sergei's fix for: Bug 983685: innodb_
data_file_ path is not written to backup-my.cnf
Regression introduced by fix for bug #733651.
Along with innodb_data_file_ path, innodb_ log_group_ home_dir is also missed. - 423. By Stewart Smith
-
merge Sergei's fix for: Bug #983720: ib_lru_dump and --galera-info fail with --stream=xbstream
- 421. By Alexey Kopytov
-
Bug #977998: --stream=tar fails (archive_
write_header failed) The problem was in the USTAR format used by XtraBackup which is
incompatible with files larger than 8 GB.Fixed by changing the libarchive format to 'restricted PAX' which avoids
the limitation. However, the PAX format generates some annoying (and
benign) warnings when the GNU tar format is used due to extended
attributes written to the tar stream by libarchive in the PAX mode. This
problem was fixed by modifying the bundled libarchive code to suppress
the extended attributes.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://qastaging/percona-xtrabackup/2.1