Percona XtraBackup moved to https://jira.percona.com/projects/PXB

Merge lp:~hrvojem/percona-xtrabackup/bug1177237-2.1 into lp:percona-xtrabackup/2.1

  1. bug1177237-2.1
  2. Merge into 2.1
Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Alexey Kopytov
Approved revision: no longer in the source branch.
Merged at revision: 591
Proposed branch: lp:~hrvojem/percona-xtrabackup/bug1177237-2.1
Merge into: lp:percona-xtrabackup/2.1
Diff against target: 40 lines (+4/-4)
2 files modified
doc/source/release-notes/2.0/2.0.7.rst (+1/-1)
doc/source/release-notes/2.1/2.1.0-rc1.rst (+3/-3)
To merge this branch: bzr merge lp:~hrvojem/percona-xtrabackup/bug1177237-2.1
Reviewer Review Type Date Requested Status
Alexey Kopytov (community) Approve
Review via email: mp+162716@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Alexey Kopytov (akopytov) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/release-notes/2.0/2.0.7.rst'
2--- doc/source/release-notes/2.0/2.0.7.rst 2013-05-06 13:52:03 +0000
3+++ doc/source/release-notes/2.0/2.0.7.rst 2013-05-07 07:05:34 +0000
4@@ -15,7 +15,7 @@
5
6 Time interval between checks done by log copying thread is now configurable by :option:`innobackupex --log-copy-interval`. Making the interval configurable allows to reduce the time between checks which can prevent |XtraBackup| failures that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread.
7
8- |Percona XtraBackup| now stores the ``GTID`` value in the :file:`xtrabackup_binlog_info` when doing the backup of |MySQL| and |Percona Server| 5.6 with the :option:`innobackupex --slave-info`. Example of how this information can be used to create/restore a slave can be found in `this blogpost <http://www.mysqlperformanceblog.com/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/>`_.
9+ |Percona XtraBackup| now stores the ``GTID`` value in the :file:`xtrabackup_binlog_info` when doing the backup of |MySQL| and |Percona Server| 5.6 with the ``GTID`` mode enabled. Example of how this information can be used to create/restore a slave can be found in `this blogpost <http://www.mysqlperformanceblog.com/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/>`_.
10
11 |Percona XtraBackup| option :option:`xtrabackup --export` now supports transportable tablespaces introduced in |MySQL| 5.6. This option can be used to produce 5.6-style metadata files, that can be imported by ``ALTER TABLE IMPORT TABLESPACE`` on |MySQL| and |Percona Server| 5.6 as described in :ref:`export_import_tables` guide.
12
13
14=== modified file 'doc/source/release-notes/2.1/2.1.0-rc1.rst'
15--- doc/source/release-notes/2.1/2.1.0-rc1.rst 2013-05-06 13:56:37 +0000
16+++ doc/source/release-notes/2.1/2.1.0-rc1.rst 2013-05-07 07:05:34 +0000
17@@ -2,7 +2,7 @@
18 |Percona XtraBackup| 2.1.0-rc1
19 =======================================
20
21-Percona is glad to announce the release of |Percona XtraBackup| 2.1.0-rc1 on May 7th 2013. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/2.1.0-rc1/>`_. For this *RC* release, we will not be making APT and YUM repositories available, just base deb and RPM packages
22+Percona is glad to announce the release of |Percona XtraBackup| 2.1.0-rc1 on May 7th 2013. Downloads are available from our download site `here <http://www.percona.com/downloads/XtraBackup/2.1.0-rc1/>`_. For this *RC* release, we will not be making APT and YUM repositories available, just base deb and RPM packages.
23
24 This is an *Release Candidate* quality release and is not intended for production. If you want a high quality, Generally Available release, the current Stable version should be used (currently 2.0.7 in the 2.0 series at the time of writing).
25
26@@ -15,7 +15,7 @@
27
28 Time interval between checks done by log copying thread is now configurable by :option:`innobackupex --log-copy-interval`. Making the interval configurable allows to reduce the time between checks which can prevent |XtraBackup| failures that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread.
29
30- |Percona XtraBackup| now stores the ``GTID`` value in the :file:`xtrabackup_binlog_info` when doing the backup of |MySQL| and |Percona Server| 5.6 with the :option:`innobackupex --slave-info`. Example of how this information can be used to create/restore a slave can be found in `this blogpost <http://www.mysqlperformanceblog.com/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/>`_.
31+ |Percona XtraBackup| now stores the ``GTID`` value in the :file:`xtrabackup_binlog_info` when doing the backup of |MySQL| and |Percona Server| 5.6 with the ``GTID`` mode enabled. Example of how this information can be used to create/restore a slave can be found in `this blogpost <http://www.mysqlperformanceblog.com/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/>`_.
32
33 |Percona XtraBackup| option :option:`xtrabackup --export` now supports transportable tablespaces introduced in |MySQL| 5.6. This option can be used to produce 5.6-style metadata files, that can be imported by ``ALTER TABLE IMPORT TABLESPACE`` on |MySQL| and |Percona Server| 5.6 as described in :ref:`export_import_tables` guide.
34
35@@ -40,4 +40,4 @@
36
37 For the *Debian* and the *Linux* binaries, the :option:`--version` message which should include the revision was showing "undefined". Bug fixed :bug:`1171721`.
38
39-Other bugs fixed: bug fixed :bug:`1088307`, bug fixed :bug:`1088309`, bug fixed :bug:`1170340`,
40+Other bugs fixed: bug fixed :bug:`1088307`, bug fixed :bug:`1088309`, bug fixed :bug:`1170340`.

Subscribers

People subscribed via source and target branches