Author: shinz
Date: 2006-08-22 19:35:03 +0200 (Tue, 22 Aug 2006)
New Revision: 3086
Log:
LOAD {DATA|TABLE} FROM MASTER is deprecated and will be removed in a future version; this is true for 5.0 and 4.1, too ( thanks for clarifying, Lars! )
Modified:
trunk/refman-4.1/replication.xml
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/replication.xml
trunk/refman-5.0/sql-syntax.xml
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2006-08-22 16:54:05 UTC (rev 3085)
+++ trunk/refman-4.1/replication.xml 2006-08-22 17:35:03 UTC (rev 3086)
Changed blocks: 3, Lines Added: 0, Lines Deleted: 63; 3659 bytes
@@ -163,30 +163,6 @@
</para>
<para>
- One way to copy the master's data to the slave is to use the
- <literal>LOAD DATA FROM MASTER</literal> statement. However,
- <literal>LOAD DATA FROM MASTER</literal> is available only as of
- MySQL 4.0.0 and works only if all the tables on the master use the
- <literal>MyISAM</literal> storage engine. In addition, this
- statement acquires a global read lock, so no updates on the master
- are possible while the tables are being transferred to the slave.
- When we implement lock-free hot table backup, this global read
- lock will no longer be necessary.
- </para>
-
- <para>
- Due to these limitations, we recommend that at this point you use
- <literal>LOAD DATA FROM MASTER</literal> only if the dataset on
- the master is relatively small, or if a prolonged read lock on the
- master is acceptable. Although the actual speed of <literal>LOAD
- DATA FROM MASTER</literal> may vary from system to system, a good
- rule of thumb for how long it takes is 1 second per 1MB of data.
- This is a rough estimate, but you should find it fairly accurate
- if both master and slave are equivalent to 700MHz Pentium CPUs in
- performance and are connected through a 100Mbps network.
- </para>
-
- <para>
After the slave has been set up with a copy of the master's data,
it connects to the master and waits for updates to process. If the
master fails, or the slave loses connectivity with your master,
@@ -1038,33 +1014,6 @@
</programlisting>
<para>
- If you plan to use the <literal>LOAD TABLE FROM
- MASTER</literal> or <literal>LOAD DATA FROM MASTER</literal>
- statements from the slave host, you must grant this account
- additional privileges:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Grant the account the <literal>SUPER</literal> and
- <literal>RELOAD</literal> global privileges.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Grant the <literal>SELECT</literal> privilege for all
- tables that you want to load. Any master tables from which
- the account cannot <literal>SELECT</literal> will be
- ignored by <literal>LOAD DATA FROM MASTER</literal>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
For additional information about setting up user accounts and
privileges, see <xref linkend="user-account-management"/>.
</para>
@@ -4321,18 +4270,6 @@
</para>
<para>
- You can also use <literal>LOAD DATA FROM MASTER</literal>. This is
- a convenient statement that transfers a snapshot to the slave and
- adjusts the log filename and offset all at once. Be warned,
- however, that it works only for <literal>MyISAM</literal> tables
- and it may hold a read lock for a long time. It is not yet
- implemented as efficiently as we would like. If you have large
- tables, the preferred method is still to make a binary snapshot on
- the master server after executing <literal>FLUSH TABLES WITH READ
- LOCK</literal>.
- </para>
-
- <para>
<emphasis role="bold">Q</emphasis>: Does the slave need to be
connected to the master all the time?
</para>
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2006-08-22 16:54:05 UTC (rev 3085)
+++ trunk/refman-4.1/sql-syntax.xml 2006-08-22 17:35:03 UTC (rev 3086)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 0; 1110 bytes
@@ -18302,6 +18302,12 @@
</programlisting>
<remark role="help-description-begin"/>
+
+ <para role="deprecated">
+ <emphasis role="bold">This feature is deprecated.</emphasis>
+ We recommend not to use it any more. It will be removed in a
+ future version.
+ </para>
<para>
This statement takes a snapshot of the master and copies it to
@@ -18420,6 +18426,12 @@
<remark role="help-description-begin"/>
+ <para role="deprecated">
+ <emphasis role="bold">This feature is deprecated.</emphasis>
+ We recommend not to use it any more. It will be removed in a
+ future version.
+ </para>
+
<para>
Transfers a copy of the table from the master to the slave.
This statement is implemented mainly debugging <literal>LOAD
Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml 2006-08-22 16:54:05 UTC (rev 3085)
+++ trunk/refman-5.0/replication.xml 2006-08-22 17:35:03 UTC (rev 3086)
Changed blocks: 3, Lines Added: 0, Lines Deleted: 62; 3611 bytes
@@ -167,29 +167,6 @@
</para>
<para>
- One way to copy the master's data to the slave is to use the
- <literal>LOAD DATA FROM MASTER</literal> statement. However,
- <literal>LOAD DATA FROM MASTER</literal> works only if all the
- tables on the master use the <literal>MyISAM</literal> storage
- engine. In addition, this statement acquires a global read lock,
- so no updates on the master are possible while the tables are
- being transferred to the slave. When we implement lock-free hot
- table backup, this global read lock will no longer be necessary.
- </para>
-
- <para>
- Due to these limitations, we recommend that at this point you use
- <literal>LOAD DATA FROM MASTER</literal> only if the dataset on
- the master is relatively small, or if a prolonged read lock on the
- master is acceptable. Although the actual speed of <literal>LOAD
- DATA FROM MASTER</literal> may vary from system to system, a good
- rule of thumb for how long it takes is 1 second per 1MB of data.
- This is a rough estimate, but you should find it fairly accurate
- if both master and slave are equivalent to 700MHz Pentium CPUs in
- performance and are connected through a 100Mbps network.
- </para>
-
- <para>
After the slave has been set up with a copy of the master's data,
it connects to the master and waits for updates to process. If the
master fails, or the slave loses connectivity with your master,
@@ -970,33 +947,6 @@
</programlisting>
<para>
- If you plan to use the <literal>LOAD TABLE FROM
- MASTER</literal> or <literal>LOAD DATA FROM MASTER</literal>
- statements from the slave host, you must grant this account
- additional privileges:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Grant the account the <literal>SUPER</literal> and
- <literal>RELOAD</literal> global privileges.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Grant the <literal>SELECT</literal> privilege for all
- tables that you want to load. Any master tables from which
- the account cannot <literal>SELECT</literal> will be
- ignored by <literal>LOAD DATA FROM MASTER</literal>.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
For additional information about setting up user accounts and
privileges, see <xref linkend="user-account-management"/>.
</para>
@@ -4237,18 +4187,6 @@
</para>
<para>
- You can also use <literal>LOAD DATA FROM MASTER</literal>. This is
- a convenient statement that transfers a snapshot to the slave and
- adjusts the log filename and offset all at once. Be warned,
- however, that it works only for <literal>MyISAM</literal> tables
- and it may hold a read lock for a long time. It is not yet
- implemented as efficiently as we would like. If you have large
- tables, the preferred method is still to make a binary snapshot on
- the master server after executing <literal>FLUSH TABLES WITH READ
- LOCK</literal>.
- </para>
-
- <para>
<emphasis role="bold">Q</emphasis>: Does the slave need to be
connected to the master all the time?
</para>
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2006-08-22 16:54:05 UTC (rev 3085)
+++ trunk/refman-5.0/sql-syntax.xml 2006-08-22 17:35:03 UTC (rev 3086)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 0; 1130 bytes
@@ -20360,6 +20360,12 @@
<remark role="help-description-begin"/>
+ <para role="deprecated">
+ <emphasis role="bold">This feature is deprecated.</emphasis>
+ We recommend not to use it any more. It will be removed in a
+ future version.
+ </para>
+
<para>
This statement takes a snapshot of the master and copies it to
the slave. It updates the values of
@@ -20477,6 +20483,12 @@
<remark role="help-description-begin"/>
+ <para role="deprecated">
+ <emphasis role="bold">This feature is deprecated.</emphasis>
+ We recommend not to use it any more. It will be removed in a
+ future version.
+ </para>
+
<para>
Transfers a copy of the table from the master to the slave.
This statement is implemented mainly debugging <literal>LOAD
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3086 - in trunk: refman-4.1 refman-5.0 | stefan | 22 Aug |
