Author: paul
Date: 2008-09-29 22:53:19 +0200 (Mon, 29 Sep 2008)
New Revision: 11914
Log:
r34315@frost: paul | 2008-09-29 15:43:25 -0500
6.0.8: The MySQL Backup tables were renamed:
online_backup -> backup_history
online_backup_progress -> backup_progress
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/refman-6.0/backup.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:34313
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33355
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:34315
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33355
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-09-29 20:01:52 UTC (rev 11913)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-09-29 20:53:19 UTC (rev 11914)
Changed blocks: 1, Lines Added: 26, Lines Deleted: 0; 912 bytes
@@ -27809,4 +27809,30 @@
</logentry>
+ <logentry entrytype="feature">
+
+ <tags>
+ <manual type="MySQL Backup"/>
+ <highlight type="incompatiblechange"/>
+ </tags>
+
+ <versions>
+ <version ver="6.0.8"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The names of the MySQL Backup tables in the
+ <literal>mysql</literal> database have been changed from
+ <literal>online_backup</literal> and
+ <literal>online_backup_progress</literal> to
+ <literal>backup_history</literal> and
+ <literal>backup_progress</literal>.
+ </para>
+
+ </message>
+
+ </logentry>
+
</changelog>
Modified: trunk/refman-6.0/backup.xml
===================================================================
--- trunk/refman-6.0/backup.xml 2008-09-29 20:01:52 UTC (rev 11913)
+++ trunk/refman-6.0/backup.xml 2008-09-29 20:53:19 UTC (rev 11914)
Changed blocks: 9, Lines Added: 28, Lines Deleted: 27; 5718 bytes
@@ -1778,19 +1778,21 @@
<listitem>
<para>
- The server maintains <literal>online_backup</literal> and
- <literal>online_backup_progress</literal> tables in the
+ The server maintains <literal>backup_history</literal> and
+ <literal>backup_progress</literal> tables in the
<literal>mysql</literal> database that contain metadata. (If
you upgrade to MySQL 6.0.5 or later from an older version,
be sure to run <command>mysql_upgrade</command> to ensure
- that these tables exist.)
+ that these tables exist. From MySQL 6.0.5 through 6.0.7,
+ these table were named <literal>online_backup</literal> and
+ <literal>online_backup_progress</literal>.)
</para>
<itemizedlist>
<listitem>
<para>
- The <literal>online_backup</literal> table contains a
+ The <literal>backup_history</literal> table contains a
row for each backup and restore operation. A row is
created when an operation begins and is updated as the
operation progresses. The rows in this table serve as a
@@ -1806,13 +1808,13 @@
<listitem>
<para>
- The <literal>online_backup_progress</literal> table
- contains progress data describing the steps in the most
- recent backup or restore operation. There may be
- multiple rows for the operation. Rows are added to this
- table over the course of the operation and are not
- updated. This enables the table to be used to track the
- current progress of the operation. Each row in the table
+ The <literal>backup_progress</literal> table contains
+ progress data describing the steps in the most recent
+ backup or restore operation. There may be multiple rows
+ for the operation. Rows are added to this table over the
+ course of the operation and are not updated. This
+ enables the table to be used to track the current
+ progress of the operation. Each row in the table
represents a step in the operation and may contain
informational statements, errors, and other pertinent
information. The data in this table has a limited
@@ -1828,8 +1830,8 @@
<para>
Currently, there are no
<literal>INFORMATION_SCHEMA</literal> tables corresponding
- to the <literal>online_backup</literal> and
- <literal>online_backup_progress</literal> tables.
+ to the <literal>backup_history</literal> and
+ <literal>backup_progress</literal> tables.
</para>
</listitem>
@@ -1844,11 +1846,11 @@
</remark>
<para>
- The <literal>online_backup</literal> table has this structure:
+ The <literal>backup_history</literal> table has this structure:
</para>
<programlisting>
-CREATE TABLE online_backup (
+CREATE TABLE backup_history (
backup_id BIGINT UNSIGNED PRIMARY KEY AUTO_INCREMENT,
process_id INT UNSIGNED NOT NULL,
binlog_pos INT UNSIGNED DEFAULT 0,
@@ -1868,11 +1870,11 @@
user_comment VARCHAR (200) DEFAULT NULL,
command VARCHAR (512),
engines VARCHAR (100),
-) ENGINE=MYISAM;
+) ENGINE=CSV CHARSET=utf8;
</programlisting>
<para>
- The <literal>online_backup</literal> columns are used as
+ The <literal>backup_history</literal> columns are used as
follows:
</para>
@@ -1887,7 +1889,7 @@
The ID for the table row. <literal>BACKUP DATABASE</literal>
and <literal>RESTORE</literal> return a result set
containing a backup ID, which is the value that tells you
- which row in the <literal>online_backup</literal> table
+ which row in the <literal>backup_history</literal> table
corresponds to the backup or restore operation.
</para>
</listitem>
@@ -2053,12 +2055,11 @@
</itemizedlist>
<para>
- The <literal>online_backup_progress</literal> table has this
- structure:
+ The <literal>backup_progress</literal> table has this structure:
</para>
<programlisting>
-CREATE TABLE online_backup_progress (
+CREATE TABLE backup_progress (
backup_id BIGINT UNSIGNED NOT NULL
object CHAR (30) NOT NULL
start_time DATATIME
@@ -2067,12 +2068,12 @@
progress BIGINT UNSIGNED
error_num INT NOT NULL DEFAULT 0
notes CHAR(100)
-) ENGINE=MYISAM;
+) ENGINE=CSV CHARSET=utf8;
</programlisting>
<para>
- The <literal>online_backup_progress</literal> columns are used
- as follows:
+ The <literal>backup_progress</literal> columns are used as
+ follows:
</para>
<itemizedlist>
@@ -2084,9 +2085,9 @@
<para>
The <literal>backup_id</literal> value of the
- <literal>online_backup</literal> table row with which the
- rows in the <literal>online_backup_progress</literal> table
- are associated.
+ <literal>backup_history</literal> table row with which the
+ rows in the <literal>backup_progress</literal> table are
+ associated.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11914 - in trunk: . dynamic-docs/changelog refman-6.0 | paul.dubois | 29 Sep |
