Author: paul
Date: 2006-02-21 16:43:14 +0100 (Tue, 21 Feb 2006)
New Revision: 1417
Log:
r8008@frost: paul | 2006-02-21 09:42:22 -0600
Don't make implied promises.
Modified:
trunk/
trunk/refman-4.1/replication.xml
trunk/refman-5.0/replication.xml
trunk/refman-5.1/replication.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:7999
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3463
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8008
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3463
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2006-02-21 15:02:35 UTC (rev 1416)
+++ trunk/refman-4.1/replication.xml 2006-02-21 15:43:14 UTC (rev 1417)
@@ -1859,8 +1859,7 @@
this, there are problems if the slave is stopped in the middle
of a <literal>BEGIN</literal>/<literal>COMMIT</literal> block
because the slave restarts at the beginning of the
- <literal>BEGIN</literal> block. This issue is on our TODO and
- will be fixed in the near future.
+ <literal>BEGIN</literal> block.
</para>
</listitem>
@@ -2041,14 +2040,6 @@
</listitem>
</orderedlist>
-
- <remark role="todo">
- [pd] Is this a promise we should make?
- </remark>
-
- <para>
- We plan to fix this problem in the near future.
- </para>
</listitem>
<listitem>
@@ -2484,17 +2475,12 @@
report-host=db-slave.mycompany.com
</programlisting>
- <remark role="todo">
- [pd] Is this a promise we should make?
- </remark>
-
<para>
The following list describes startup options for controlling
replication. Many of these options can be reset while the server
is running by using the <literal>CHANGE MASTER TO</literal>
statement. Others, such as the <option>--replicate-*</option>
- options, can be set only when the slave server starts. We plan to
- fix this.
+ options, can be set only when the slave server starts.
</para>
<remark role="todo">
@@ -4215,21 +4201,16 @@
time it takes the slave to catch up.
</para>
- <remark role="todo">
- [pd] Really true that LDFM will be recommended in the future?
- </remark>
-
<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. In the future,
- <literal>LOAD DATA FROM MASTER</literal> will be the recommended
- way to set up a slave. 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>.
+ 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>
@@ -4249,8 +4230,7 @@
only sporadically and for short periods of time. The implication
of this is that, at any given time, the slave is not guaranteed to
be in synchrony with the master unless you take some special
- measures. In the future, we will have the option to block the
- master until at least one slave is synchronized.
+ measures.
</para>
<para>
Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml 2006-02-21 15:02:35 UTC (rev 1416)
+++ trunk/refman-5.0/replication.xml 2006-02-21 15:43:14 UTC (rev 1417)
@@ -1817,8 +1817,7 @@
this, there are problems if the slave is stopped in the middle
of a <literal>BEGIN</literal>/<literal>COMMIT</literal> block
because the slave restarts at the beginning of the
- <literal>BEGIN</literal> block. This issue is on our TODO and
- will be fixed in the near future.
+ <literal>BEGIN</literal> block.
</para>
</listitem>
@@ -2008,14 +2007,6 @@
</listitem>
</orderedlist>
-
- <remark role="todo">
- [pd] Is this a promise we should make?
- </remark>
-
- <para>
- We plan to fix this problem in the near future.
- </para>
</listitem>
<listitem>
@@ -2387,17 +2378,12 @@
report-host=db-slave.mycompany.com
</programlisting>
- <remark role="todo">
- [pd] Is this a promise we should make?
- </remark>
-
<para>
The following list describes startup options for controlling
replication. Many of these options can be reset while the server
is running by using the <literal>CHANGE MASTER TO</literal>
statement. Others, such as the <option>--replicate-*</option>
- options, can be set only when the slave server starts. We plan to
- fix this.
+ options, can be set only when the slave server starts.
</para>
<remark role="todo">
@@ -4097,21 +4083,16 @@
time it takes the slave to catch up.
</para>
- <remark role="todo">
- [pd] Really true that LDFM will be recommended in the future?
- </remark>
-
<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. In the future,
- <literal>LOAD DATA FROM MASTER</literal> will be the recommended
- way to set up a slave. 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>.
+ 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>
@@ -4131,8 +4112,7 @@
only sporadically and for short periods of time. The implication
of this is that, at any given time, the slave is not guaranteed to
be in synchrony with the master unless you take some special
- measures. In the future, we will have the option to block the
- master until at least one slave is synchronized.
+ measures.
</para>
<para>
Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml 2006-02-21 15:02:35 UTC (rev 1416)
+++ trunk/refman-5.1/replication.xml 2006-02-21 15:43:14 UTC (rev 1417)
@@ -1990,8 +1990,7 @@
this, there are problems if the slave is stopped in the middle
of a <literal>BEGIN</literal>/<literal>COMMIT</literal> block
because the slave restarts at the beginning of the
- <literal>BEGIN</literal> block. This issue is on our TODO and
- will be fixed in the near future.
+ <literal>BEGIN</literal> block.
</para>
</listitem>
@@ -2178,21 +2177,6 @@
</listitem>
</orderedlist>
-
- <remark role="note">
- [js] Ive commented this out, since RBR fixes the problem,
- correct?
- </remark>
-
-<!--
- <remark role="todo">
- [pd] Is this a promise we should make?
- </remark>
-
- <para>
- We plan to fix this problem in the near future.
- </para>
--->
</listitem>
<listitem>
@@ -2568,17 +2552,12 @@
report-host=db-slave.mycompany.com
</programlisting>
- <remark role="todo">
- [pd] Is this a promise we should make?
- </remark>
-
<para>
The following list describes startup options for controlling
replication. Many of these options can be reset while the server
is running by using the <literal>CHANGE MASTER TO</literal>
statement. Others, such as the <option>--replicate-*</option>
- options, can be set only when the slave server starts. We plan to
- fix this.
+ options, can be set only when the slave server starts.
</para>
<remark role="todo">
@@ -4311,21 +4290,16 @@
time it takes the slave to catch up.
</para>
- <remark role="todo">
- [pd] Really true that LDFM will be recommended in the future?
- </remark>
-
<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. In the future,
- <literal>LOAD DATA FROM MASTER</literal> will be the recommended
- way to set up a slave. 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>.
+ 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>
@@ -4345,8 +4319,7 @@
only sporadically and for short periods of time. The implication
of this is that, at any given time, the slave is not guaranteed to
be in synchrony with the master unless you take some special
- measures. In the future, we will have the option to block the
- master until at least one slave is synchronized.
+ measures.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1417 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 21 Feb |
