List:Commits« Previous MessageNext Message »
From:jon Date:October 4 2007 8:49am
Subject:svn commit - mysqldoc@docsrva: r7967 - in trunk: refman-5.1 refman-5.2
View as plain text  
Author: jstephens
Date: 2007-10-04 10:49:53 +0200 (Thu, 04 Oct 2007)
New Revision: 7967

Log:

ndb_apply_status is populated only on replication slaves 
(Thanks, Hartmut!)



Modified:
   trunk/refman-5.1/mysql-cluster-replication.xml
   trunk/refman-5.2/mysql-cluster-replication.xml


Modified: trunk/refman-5.1/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication.xml	2007-10-04 06:00:04 UTC (rev 7966)
+++ trunk/refman-5.1/mysql-cluster-replication.xml	2007-10-04 08:49:53 UTC (rev 7967)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 1; 957 bytes

@@ -758,7 +758,6 @@
       specific to any one SQL node in the (slave) cluster, and so
       <literal>ndb_apply_status</literal> can use the <literal>NDB
       Cluster</literal> storage engine, as shown here:
-    </para>
 
 <programlisting>
 CREATE TABLE `ndb_apply_status` (

@@ -771,6 +770,10 @@
 ) ENGINE=NDBCLUSTER   DEFAULT CHARSET=latin1;
 </programlisting>
 
+      However, this table is populated only on a replication slave; on
+      the master, no <literal>DataMemory</literal> is allocated to it.
+    </para>
+
     <para>
       The <literal>log_name</literal>, <literal>start_pos</literal>, and
       <literal>end_pos</literal> columns were added in MySQL 5.1.18.


Modified: trunk/refman-5.2/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-replication.xml	2007-10-04 06:00:04 UTC (rev 7966)
+++ trunk/refman-5.2/mysql-cluster-replication.xml	2007-10-04 08:49:53 UTC (rev 7967)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 1; 889 bytes

@@ -772,7 +772,6 @@
       specific to any one SQL node in the (slave) cluster, and so
       <literal>ndb_apply_status</literal> can use the <literal>NDB
       Cluster</literal> storage engine, as shown here:
-    </para>
 
 <programlisting>
 CREATE TABLE `ndb_apply_status` (

@@ -785,6 +784,10 @@
 ) ENGINE=NDBCLUSTER   DEFAULT CHARSET=latin1;
 </programlisting>
 
+      However, this table is populated only on a replication slave; on
+      the master, no <literal>DataMemory</literal> is allocated to it.
+    </para>
+
     <important>
       <para>
         If you are using MySQL Cluster replication, see


Thread
svn commit - mysqldoc@docsrva: r7967 - in trunk: refman-5.1 refman-5.2jon4 Oct