lp:~sergei.glushchenko/percona-xtrabackup/xb20-partial

Created by Sergei Glushchenko on 2012-08-26 and last modified on 2013-01-02
Get this branch:
bzr branch lp:~sergei.glushchenko/percona-xtrabackup/xb20-partial
Only Sergei Glushchenko can upload to this branch. If you are Sergei Glushchenko please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Recent revisions

481. By Sergei Glushchenko on 2013-01-02

Bug 711166
Partitioned tables are not correctly handled by the --databases, --include,
--tables-file options of innobackupex, and by the --tables and
--tables-file options of xtrabackup.
Solution is to remove partition suffix (#P#...) before doing filtering.
Testcases cover variants of using filtering options with MyISAM and
InnoDB tables (to test both innobackupex and xtrabackup) with either stream
mode turned on and turned off.

479. By Alexey Kopytov on 2012-11-21

Merged from trunk.

478. By Alexey Kopytov on 2012-11-14

Bug #1055989: innobackupex waits for streaming temporary log file to
              finish before unlocking tables

The problem was that in XtraBackup 2.0 streaming xtrabackup_logfile from
a temporary file was performed in the xtrabackup binary and
innobackupex waited for the xtrabackup process to exit before unlocking
the tables. Streaming the log file might take a long time, while
unnecessarily keeping the server locked with FTWRL. In fact, releasing
the lock can be performed as soon as the xtrabackup binary stops
duplicating the redo log.

Fixed by:

- splitting resume_ibbackup() into two functions. resume_ibbackup()
  itself now resumes the xtrabackup process and then just waits for the
  log copying to stop rather than process termination as previously. The
  new function wait_for_ibbackup_finish() now waits for process
  termination and obtains its exit status. This function is called after
  releasing the FTWRL lock.

- implementing a new synchronization point between innobackupex and
  xtrabackup using the same mechanism (the xtrabackup_suspended file)
  which is used for synchronization before starting FTWRL: when
  innobackupex wants to wait until log copying finishes, it removes
  xtrabackup_suspended and waits until it is created again by
  xtrabackup. So xtrabackup creates the file to signal innobackupex when
  log copying is complete and it is now safe to release the FTWRL lock.

477. By Stewart Smith on 2012-11-08

merge aio fixes

476. By Stewart Smith on 2012-11-07

merge fix for Bug #528752: xtrabackup does not handle innodb=force in my.cnf

475. By Stewart Smith on 2012-11-07

merge docs fixes

474. By Stewart Smith on 2012-11-07

merge 2.0.3 release tree

473. By Stewart Smith on 2012-10-31

merge lintian fixes

472. By Hrvoje Matijakovic on 2012-10-29

 * bugfixes for bugs: Bug #1066836, Bug #1059945, Bug #1065761

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:percona-xtrabackup/2.1
This branch contains Public information 
Everyone can see this information.