From: Date: October 24 2008 6:41pm
Subject: svn commit - mysqldoc@docsrva: r12146 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0
List-Archive: http://lists.mysql.com/commits/57034
Message-Id: <200810241641.m9OGfgk5030158@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Author: jstephens
Date: 2008-10-24 18:41:42 +0200 (Fri, 24 Oct 2008)
New Revision: 12146
Log:
Replicated queries don't get written to the slow query log on the slave
Fixes docs part of Bug #23300
Modified:
trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/replication.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/replication-notes.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/replication-notes.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/replication-notes.xml
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-4.1/dba-core.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 709 bytes
@@ -11010,6 +11010,13 @@
presence of an index because the table has zero rows or one row.
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master. This is a known issue which we intend
+ to fix in a future version of MySQL. (Bug #23300)
+
+
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-4.1/replication.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 686 bytes
@@ -2165,6 +2165,15 @@
+
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master. This is a known issue which we intend
+ to fix in a future version of MySQL. (Bug #23300)
+
+
+
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-5.0/dba-core.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 709 bytes
@@ -12896,6 +12896,13 @@
presence of an index because the table has zero rows or one row.
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master. This is a known issue which we intend
+ to fix in a future version of MySQL. (Bug #23300)
+
+
Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-5.0/replication-notes.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 4, Lines Added: 54, Lines Deleted: 37; 5451 bytes
@@ -553,6 +553,23 @@
+
+
+ Replication and the Slow Query Log
+
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master.
+
+
+
+ This is a known issue which we intend to fix in a future version
+ of MySQL. (Bug #23300)
+
+
+
+
Replication During a Master Crash
@@ -1071,17 +1088,15 @@
-
-
Replication Compatibility Between MySQL Versions
-
+
MySQL supports replication from one major version to the next
higher major version. For example, you can replicate from a master
running MySQL 4.1 to a slave running MySQL 5.0, from a master
running MySQL 5.0 to a slave running MySQL 5.1, and so on.
-
+
In some cases, it is also possible to replicate between a master
and a slave that is more than one major version newer than the
@@ -1094,7 +1109,7 @@
server to a MySQL 5.0 server, and then from the MySQL 5.0 server
to a MySQL 5.1 server.
-
+
We recommend using the most recent release available within a
@@ -1105,87 +1120,89 @@
become available for that major version.
-
+
Replication from newer masters to older slaves may be possible,
but is generally not supported. This is due to a number of
factors:
-
+
-
+
-
+
Binary log format changes
-
+
The binary log format can change between major releases.
While we attempt to maintain backwards compatiblity, this is
- not always possible. Major changes were made in MySQL 5.0.3 (for
- improvements to handling of character sets and LOAD DATA
- INFILE) and 5.0.4 (for improvements to handling of time
- zones). Because of these changes, replication from a MySQL 5.0.3 or
- later master to a MySQL 5.0.2 or earlier slave is not supported.
- This also means that replication from a MySQL 5.0.3 (or
- later) master to any MySQL 4.1 (or earlier) slave is generally not
- supported.
+ not always possible. Major changes were made in MySQL 5.0.3
+ (for improvements to handling of character sets and
+ LOAD DATA INFILE) and 5.0.4 (for
+ improvements to handling of time zones). Because of these
+ changes, replication from a MySQL 5.0.3 or later master to a
+ MySQL 5.0.2 or earlier slave is not supported. This also
+ means that replication from a MySQL 5.0.3 (or later) master
+ to any MySQL 4.1 (or earlier) slave is generally not
+ supported.
-
+
-
+
- This also has significant implications for upgrading replication
- servers; see , for more
- information.
+ This also has significant implications for upgrading
+ replication servers; see
+ , for more information.
-
+
-
+
Use of row-based replication
-
+
You cannot replicate using row-based replication from a
MySQL 5.1.5 or later master to a slave running an earlier
version of MySQL, since MySQL versions prior to 5.1.5 do not
support RBR.
-
+
-
+
- Row-based replication is not available in MySQL ¤t-series;.
- For more information about row-based replication in MySQL 5.1, see
+ Row-based replication is not available in MySQL
+ ¤t-series;. For more information about row-based
+ replication in MySQL 5.1, see
.
-
+
-
+
SQL incompatiblities
-
+
You cannot replicate from a newer master to an older slave
using statement-based replication if the statements to be
replicated use SQL features available on the master but not
on the slave.
-
+
-
+
-
+
For more information on potential replication issues, see
.
-
+
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-5.1/dba-core.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 709 bytes
@@ -14921,6 +14921,13 @@
presence of an index because the table has zero rows or one row.
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master. This is a known issue which we intend
+ to fix in a future version of MySQL. (Bug #23300)
+
+
Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-5.1/replication-notes.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 2, Lines Added: 24, Lines Deleted: 7; 1896 bytes
@@ -1051,6 +1051,23 @@
+
+
+ Replication and the Slow Query Log
+
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master.
+
+
+
+ This is a known issue which we intend to fix in a future version
+ of MySQL. (Bug #23300)
+
+
+
+
Replication During a Master Crash
@@ -2030,17 +2047,17 @@
implemented in MySQL 5.0 changed considerably from that used
in previous versions, especially with regard to handling of
character sets, LOAD DATA INFILE, and
- time zones. This means that replication from a
- MySQL 5.0 (or later) master to a MySQL 4.1 (or earlier)
- slave is generally not supported.
+ time zones. This means that replication from a MySQL 5.0 (or
+ later) master to a MySQL 4.1 (or earlier) slave is generally
+ not supported.
-
+
- This also has significant implications for upgrading replication
- servers; see , for more
- information.
+ This also has significant implications for upgrading
+ replication servers; see
+ , for more information.
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-6.0/dba-core.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 709 bytes
@@ -14948,6 +14948,13 @@
presence of an index because the table has zero rows or one row.
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master. This is a known issue which we intend
+ to fix in a future version of MySQL. (Bug #23300)
+
+
Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml 2008-10-24 16:14:32 UTC (rev 12145)
+++ trunk/refman-6.0/replication-notes.xml 2008-10-24 16:41:42 UTC (rev 12146)
Changed blocks: 1, Lines Added: 17, Lines Deleted: 0; 873 bytes
@@ -1018,6 +1018,23 @@
+
+
+ Replication and the Slow Query Log
+
+
+ Replication slaves do not write replicated queries to the slow
+ query log, even if the same queries were written to the slow
+ query log on the master.
+
+
+
+ This is a known issue which we intend to fix in a future version
+ of MySQL. (Bug #23300)
+
+
+
+
Replication During a Master Crash