lp://staging/~sergei.glushchenko/percona-xtrabackup/buffer_pool_dump-2.0

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

542. By Sergei Glushchenko on 2013-04-25

Blueprint: Support InnoDB buffer pool dumps in MySQL 5.6
https://blueprints.launchpad.net/percona-xtrabackup/+spec/support-56-buffer-pool-dumps
MySQL 5.6 adds an ability to dump the buffer pool into file for it to be
possible to load it into memory at startup or on demand. The location of
buffer pool file is set by global variable innodb_buffer_pool_filename
and is relative to MySQL data directory.
The patch adds an ability to take a backup of buffer pool dump. It has been
made exactly the same way as XtraDB LRU dump is backed up.
Three tests have been added for this feature. One takes regular backup and
after takes streaming backup. Another one takes backup with --rsync
option. Third test tests feature with incremental backups.

541. By Alexey Kopytov on 2013-04-25

Merged lp:~akopytov/percona-xtrabackup/bug1170806-2.0.

540. By Alexey Kopytov on 2013-04-25

Merged lp:~akopytov/percona-xtrabackup/support-gtid-2.0.

539. By Alexey Kopytov on 2013-04-25

Manual merge of lp:~ignacio-nin/percona-xtrabackup/2.0-bug1171721.

538. By Alexey Kopytov on 2013-04-24

Added the InnoDB: prefix for error messages erroneously removed by the
fix for bug #1169971.

537. By Alexey Kopytov on 2013-04-24

Merged lp:~sergei.glushchenko/percona-xtrabackup/21-bug856400.

536. By Alexey Kopytov on 2013-04-24

Merged lp:~ignacio-nin/percona-xtrabackup/2.0-dpkg-revamp.

535. By Alexey Kopytov on 2013-04-24

Merged lp:~ignacio-nin/percona-xtrabackup/2.0-dpkg-dummy-revamp.

534. By Alexey Kopytov on 2013-04-23

Implementation of
https://blueprints.launchpad.net/percona-xtrabackup/+spec/support-56-innodb-page-size

innodb_page_size was only handled by XtraDB-based binaries, but ignored
by xtrabackup_56, since it is not XtraDB-based.

This revision also removes innodb_file_per_table from --print-param,
since it was not used by anything and is not required on any backup
stage.

533. By Alexey Kopytov on 2013-04-22

Implementation of
https://blueprints.launchpad.net/percona-xtrabackup/+spec/support-separate-undo-tablespace

In order to backup separate undo tablespaces they must be added in the
fil_system list of tablespaces on the backup stage. This is implemented
in srv_undo_tablespaces_init(), which needs some modifications for
XtraBackup. First, create_new_db is always FALSE in XtraBackup. We also
need another argument to check if we can read the number of currently
used undo tablespaces from the trx header. We can't do that on the
backup stage, so we just do what srv_undo_tablespaces_init() would do in
'create_new_db == TRUE' mode, i.e. just assume the number of available
undo tablespaces is the number of used tablespaces.

We also have to restore undo tablespaces on --copy-back (unlike
e.g. separate doublewrite tablespace in PS). The reasons are that:

1) the server would refuse to start if the number of available undo
tablespaces is less than the number of configured ones.

2) we can prepare the backup with --redo-only (i.e. let the server
rollback uncommitted transactions)

There were also some tweaks to the test suite required to create a test
case. Previously my.cnf was only used by xtrabackup, but not the server
itself (one had to pass arguments to start_server and then add the same
arguments to my.cnf for xtrabackup to "see" them). Now my.cnf is used by
both server and xtrabackup, and it is possible to add custom entries to
my.cnf using the MYSQLD_EXTRA_MY_CNF_OPTS variable.

This patch also fixes bug #1169971: "Lost InnoDB messages in
xtrabackup_56".