Author: jstephens
Date: 2007-06-10 17:04:41 +0200 (Sun, 10 Jun 2007)
New Revision: 6746
Log:
Moved binary logging items from Performance Limitations to Limitations
Exclusive to MySQL Cluster, added indexterms (thanks, Todd!)
Modified:
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.1/mysql-cluster.xml
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2007-06-10 04:04:13 UTC (rev 6745)
+++ trunk/refman-4.1/mysql-cluster.xml 2007-06-10 15:04:41 UTC (rev 6746)
Changed blocks: 2, Lines Added: 88, Lines Deleted: 78; 5846 bytes
@@ -18293,84 +18293,6 @@
</formalpara>
</listitem>
- <listitem>
- <formalpara>
-
- <title>Binary logging</title>
-
- <para>
- MySQL Cluster has the following limitations or
- restrictions with regard to binary logging:
-
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>SQL_LOG_BIN</literal> has no effect on
- data operations; however, it is supported for
- schema operations.
- </para>
- </listitem>
-
- <listitem>
- <para>
- MySQL Cluster cannot produce a binlog for tables
- having <literal>BLOB</literal> columns but no
- primary key.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Only the following schema operations are logged in
- a cluster binlog which is <emphasis>not</emphasis>
- on the <command>mysqld</command> executing the
- statement:
-
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>CREATE TABLE</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>ALTER TABLE</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>DROP TABLE</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>CREATE DATABASE</literal> /
- <literal>CREATE SCHEMA</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>DROP DATABASE</literal> /
- <literal>DROP SCHEMA</literal>
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
- </listitem>
-
</itemizedlist>
</para>
@@ -18476,6 +18398,94 @@
</formalpara>
</listitem>
+ <listitem>
+ <formalpara>
+
+ <title>Binary logging</title>
+
+ <indexterm>
+ <primary>MySQL Cluster limitations</primary>
+ <secondary>binary logging</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>binary logging</primary>
+ <secondary>and MySQL Cluster</secondary>
+ </indexterm>
+
+ <para>
+ MySQL Cluster has the following limitations or
+ restrictions with regard to binary logging:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>SQL_LOG_BIN</literal> has no effect on
+ data operations; however, it is supported for
+ schema operations.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster cannot produce a binlog for tables
+ having <literal>BLOB</literal> columns but no
+ primary key.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Only the following schema operations are logged in
+ a cluster binlog which is <emphasis>not</emphasis>
+ on the <command>mysqld</command> executing the
+ statement:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>CREATE TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ALTER TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CREATE DATABASE</literal> /
+ <literal>CREATE SCHEMA</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP DATABASE</literal> /
+ <literal>DROP SCHEMA</literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+ </listitem>
+
</itemizedlist>
See also
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2007-06-10 04:04:13 UTC (rev 6745)
+++ trunk/refman-5.0/mysql-cluster.xml 2007-06-10 15:04:41 UTC (rev 6746)
Changed blocks: 2, Lines Added: 88, Lines Deleted: 78; 5846 bytes
@@ -18380,84 +18380,6 @@
</formalpara>
</listitem>
- <listitem>
- <formalpara>
-
- <title>Binary logging</title>
-
- <para>
- MySQL Cluster has the following limitations or
- restrictions with regard to binary logging:
-
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>SQL_LOG_BIN</literal> has no effect on
- data operations; however, it is supported for
- schema operations.
- </para>
- </listitem>
-
- <listitem>
- <para>
- MySQL Cluster cannot produce a binlog for tables
- having <literal>BLOB</literal> columns but no
- primary key.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Only the following schema operations are logged in
- a cluster binlog which is <emphasis>not</emphasis>
- on the <command>mysqld</command> executing the
- statement:
-
- <itemizedlist>
-
- <listitem>
- <para>
- <literal>CREATE TABLE</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>ALTER TABLE</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>DROP TABLE</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>CREATE DATABASE</literal> /
- <literal>CREATE SCHEMA</literal>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>DROP DATABASE</literal> /
- <literal>DROP SCHEMA</literal>
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
- </listitem>
-
- </itemizedlist>
- </para>
-
- </formalpara>
- </listitem>
-
</itemizedlist>
</para>
@@ -18563,6 +18485,94 @@
</formalpara>
</listitem>
+ <listitem>
+ <formalpara>
+
+ <title>Binary logging</title>
+
+ <indexterm>
+ <primary>MySQL Cluster limitations</primary>
+ <secondary>binary logging</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>binary logging</primary>
+ <secondary>and MySQL Cluster</secondary>
+ </indexterm>
+
+ <para>
+ MySQL Cluster has the following limitations or
+ restrictions with regard to binary logging:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>SQL_LOG_BIN</literal> has no effect on
+ data operations; however, it is supported for
+ schema operations.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ MySQL Cluster cannot produce a binlog for tables
+ having <literal>BLOB</literal> columns but no
+ primary key.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Only the following schema operations are logged in
+ a cluster binlog which is <emphasis>not</emphasis>
+ on the <command>mysqld</command> executing the
+ statement:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>CREATE TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ALTER TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP TABLE</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CREATE DATABASE</literal> /
+ <literal>CREATE SCHEMA</literal>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP DATABASE</literal> /
+ <literal>DROP SCHEMA</literal>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+ </listitem>
+
</itemizedlist>
See also
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2007-06-10 04:04:13 UTC (rev 6745)
+++ trunk/refman-5.1/mysql-cluster.xml 2007-06-10 15:04:41 UTC (rev 6746)
Changed blocks: 2, Lines Added: 64, Lines Deleted: 54; 4326 bytes
@@ -22237,11 +22237,75 @@
</formalpara>
</listitem>
+ </itemizedlist>
+ </para>
+
+ </section>
+
+ <section id="mysql-cluster-limitations-exclusive-to-cluster">
+
+ <title>Issues Exclusive to MySQL Cluster</title>
+
+ <indexterm>
+ <primary>MySQL Cluster limitations</primary>
+ <secondary>implementation</secondary>
+ </indexterm>
+
+ <para>
+ The following are limitations specific to the
+ <literal>NDBCLUSTER</literal> storage engine:
+
+ <itemizedlist>
+
<listitem>
<formalpara>
+ <title>Machine architecture</title>
+
+ <para>
+ All machines used in the cluster must have the same
+ architecture. That is, all machines hosting nodes must
+ be either big-endian or little-endian, and you cannot
+ use a mixture of both. For example, you cannot have a
+ management node running on a PowerPC which directs a
+ data node that is running on an x86 machine. This
+ restriction does not apply to machines simply running
+ <command>mysql</command> or other clients that may be
+ accessing the cluster's SQL nodes.
+ </para>
+
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+
+ <title>Adding and dropping of data nodes</title>
+
+ <para>
+ Online adding or dropping of data nodes is not currently
+ possible. In such cases, the entire cluster must be
+ restarted.
+ </para>
+
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+
<title>Binary logging</title>
+ <indexterm>
+ <primary>MySQL Cluster limitations</primary>
+ <secondary>binary logging</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>binary logging</primary>
+ <secondary>and MySQL Cluster</secondary>
+ </indexterm>
+
<para>
MySQL Cluster has the following limitations or
restrictions with regard to binary logging:
@@ -22352,61 +22416,7 @@
</listitem>
</itemizedlist>
- </para>
- </section>
-
- <section id="mysql-cluster-limitations-exclusive-to-cluster">
-
- <title>Issues Exclusive to MySQL Cluster</title>
-
- <indexterm>
- <primary>MySQL Cluster limitations</primary>
- <secondary>implementation</secondary>
- </indexterm>
-
- <para>
- The following are limitations specific to the
- <literal>NDBCLUSTER</literal> storage engine:
-
- <itemizedlist>
-
- <listitem>
- <formalpara>
-
- <title>Machine architecture</title>
-
- <para>
- All machines used in the cluster must have the same
- architecture. That is, all machines hosting nodes must
- be either big-endian or little-endian, and you cannot
- use a mixture of both. For example, you cannot have a
- management node running on a PowerPC which directs a
- data node that is running on an x86 machine. This
- restriction does not apply to machines simply running
- <command>mysql</command> or other clients that may be
- accessing the cluster's SQL nodes.
- </para>
-
- </formalpara>
- </listitem>
-
- <listitem>
- <formalpara>
-
- <title>Adding and dropping of data nodes</title>
-
- <para>
- Online adding or dropping of data nodes is not currently
- possible. In such cases, the entire cluster must be
- restarted.
- </para>
-
- </formalpara>
- </listitem>
-
- </itemizedlist>
-
See also
<xref linkend="mysql-cluster-limitations-multiple-nodes"/>.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6746 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 10 Jun |
