Author: jstephens
Date: 2007-10-02 15:45:37 +0200 (Tue, 02 Oct 2007)
New Revision: 7938
Log:
Fixed Docs Bug #31329.
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-02 13:06:15 UTC (rev 7937)
+++ trunk/refman-5.1/mysql-cluster-replication.xml 2007-10-02 13:45:37 UTC (rev 7938)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 4; 1141 bytes
@@ -811,10 +811,11 @@
However, it is advisable to check for the existence and integrity
of these tables as an initial step in preparing a MySQL Cluster
for replication. It is possible to view event data recorded in the
- binary log by querying the <literal>mysql.binlog_index</literal>
- table directly on the master. This can be also be accomplished
- using the <literal>SHOW BINLOG EVENTS</literal> statement on
- either the replication master or slave MySQL servers. (See
+ binary log by querying the
+ <literal>mysql.ndb_binlog_index</literal> table directly on the
+ master. This can be also be accomplished using the <literal>SHOW
+ BINLOG EVENTS</literal> statement on either the replication master
+ or slave MySQL servers. (See
<xref linkend="show-binlog-events"/>.)
</para>
Modified: trunk/refman-5.2/mysql-cluster-replication.xml
===================================================================
--- trunk/refman-5.2/mysql-cluster-replication.xml 2007-10-02 13:06:15 UTC (rev 7937)
+++ trunk/refman-5.2/mysql-cluster-replication.xml 2007-10-02 13:45:37 UTC (rev 7938)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 4; 1141 bytes
@@ -820,10 +820,11 @@
However, it is advisable to check for the existence and integrity
of these tables as an initial step in preparing a MySQL Cluster
for replication. It is possible to view event data recorded in the
- binary log by querying the <literal>mysql.binlog_index</literal>
- table directly on the master. This can be also be accomplished
- using the <literal>SHOW BINLOG EVENTS</literal> statement on
- either the replication master or slave MySQL servers. (See
+ binary log by querying the
+ <literal>mysql.ndb_binlog_index</literal> table directly on the
+ master. This can be also be accomplished using the <literal>SHOW
+ BINLOG EVENTS</literal> statement on either the replication master
+ or slave MySQL servers. (See
<xref linkend="show-binlog-events"/>.)
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7938 - in trunk: refman-5.1 refman-5.2 | jon | 2 Oct |
