| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | April 30 2007 2:18pm |
| Subject: | svn commit - mysqldoc@docsrva: r6267 - trunk/refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2007-04-30 14:18:08 +0200 (Mon, 30 Apr 2007) New Revision: 6267 Log: Reformat. Modified: trunk/refman-5.1/mysql-cluster-merged.xml Modified: trunk/refman-5.1/mysql-cluster-merged.xml =================================================================== --- trunk/refman-5.1/mysql-cluster-merged.xml 2007-04-30 12:17:33 UTC (rev 6266) +++ trunk/refman-5.1/mysql-cluster-merged.xml 2007-04-30 12:18:08 UTC (rev 6267) Changed blocks: 18, Lines Added: 69, Lines Deleted: 60; 12744 bytes @@ -2370,18 +2370,18 @@ <command>BUILD/compile-pentium-max</command> by default builds the MySQL Server with support for the <literal>InnoDB</literal> storage engine. <emphasis>You must - not deploy or make use of MySQL &mccge-series; - employing the <literal>InnoDB</literal> storage engine without - prior written permission to do so from MySQL AB</emphasis>. + not deploy or make use of MySQL &mccge-series; employing the + <literal>InnoDB</literal> storage engine without prior written + permission to do so from MySQL AB</emphasis>. </para> <para> If you wish to use <literal>InnoDB</literal> technology in - conjunction with your use of MySQL &mccge-series; and - do not already have authorization to do so as part of your - MySQL Server license, contact your MySQL AB salesperson or - other authorized MySQL AB representative for assistance in - upgrading your MySQL Server license. + conjunction with your use of MySQL &mccge-series; and do not + already have authorization to do so as part of your MySQL + Server license, contact your MySQL AB salesperson or other + authorized MySQL AB representative for assistance in upgrading + your MySQL Server license. </para> </warning> @@ -5012,10 +5012,10 @@ </para> <para> - Beginning with MySQL 5.1.15 (&mccge-series;: MySQL 5.1.15-ndb-6.1.1), this parameter takes one of - the integer values <literal>0</literal>, - <literal>1</literal>, or <literal>2</literal>, which act - as follows: + Beginning with MySQL 5.1.15 (&mccge-series;: MySQL + 5.1.15-ndb-6.1.1), this parameter takes one of the integer + values <literal>0</literal>, <literal>1</literal>, or + <literal>2</literal>, which act as follows: </para> <itemizedlist> @@ -5050,12 +5050,12 @@ <literal>1</literal> or <literal>true</literal> enabled locking of the process after its memory was allocated. <emphasis role="bold">Important</emphasis>: Beginning with - MySQL 5.1.15 (&mccge-series;: MySQL 5.1.15-ndb-6.1.1), it is no longer possible to use - <literal>true</literal> or <literal>false</literal> for - the value of this parameter; when upgrading from a - previous version, you must change the value to - <literal>0</literal>, <literal>1</literal>, or - <literal>2</literal>. + MySQL 5.1.15 (&mccge-series;: MySQL 5.1.15-ndb-6.1.1), it + is no longer possible to use <literal>true</literal> or + <literal>false</literal> for the value of this parameter; + when upgrading from a previous version, you must change + the value to <literal>0</literal>, <literal>1</literal>, + or <literal>2</literal>. </para> </listitem> @@ -5591,13 +5591,14 @@ control the write speed, this parameter specifies how many pages per 100 milliseconds are to be written. In this context, a <quote>page</quote> is defined as 8KB. This - parameter is specified in units of 80KB per second, so setting + parameter is specified in units of 80KB per second, so + setting <literal>NoOfDiskPagesToDiskAfterRestartTUP</literal> to a value of <literal>20</literal> entails writing 1.6MB in data pages to disk each second during a local checkpoint. This value includes the writing of UNDO log records for - data pages. That is, this parameter handles the limitation of writes - from data memory. (See the entry for + data pages. That is, this parameter handles the limitation + of writes from data memory. (See the entry for <literal>IndexMemory</literal> for information about index pages.) </para> @@ -5819,8 +5820,8 @@ <literal>UndoIndexBuffer</literal> and <literal>UndoDataBuffer</literal> parameters which appeared in earlier versions of MySQL Cluster are not necessary in MySQL - 5.1 (including &mccge-series;), since undo logs are no longer kept on disk for in-memory - tables. + 5.1 (including &mccge-series;), since undo logs are no longer + kept on disk for in-memory tables. </para> <para id="mysql-cluster-controlling-log-messages"> @@ -6798,10 +6799,10 @@ <emphasis role="bold">Important</emphasis>: <emphasis>SHM functionality is considered experimental only</emphasis>. It is not officially supported in any MySQL release series up to - and including MySQL ¤t-series; and &mccge-series;. This means that you must - determine for yourself or by using our free resources (forums, - mailing lists) whether it can be made to work correctly in - your specific case. + and including MySQL ¤t-series; and &mccge-series;. This + means that you must determine for yourself or by using our + free resources (forums, mailing lists) whether it can be made + to work correctly in your specific case. </para> <itemizedlist> @@ -7523,7 +7524,8 @@ </row> <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal></entry> - <entry><emphasis>As of MySQL 5.1.15 (&mccge-series;: MySQL 5.1.15-ndb-6.1.1)</emphasis>: integer; + <entry><emphasis>As of MySQL 5.1.15 (&mccge-series;: MySQL + 5.1.15-ndb-6.1.1)</emphasis>: integer; <emphasis>previously</emphasis>: true|false (<literal>1</literal>|<literal>0</literal>)</entry> <entry>0</entry> @@ -7737,7 +7739,8 @@ </row> <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-memreportfrequency">MemReportFrequency</link></literal> - (added in MySQL 5.1.16; &mccge-series;: added in MySQL 5.1.14-ndb-6.1.0)</entry> + (added in MySQL 5.1.16; &mccge-series;: added in MySQL + 5.1.14-ndb-6.1.0)</entry> <entry>integer</entry> <entry>0</entry> <entry>0</entry> @@ -7874,7 +7877,8 @@ </row> <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">TcpBind_INADDR_ANY</link></literal> - (<emphasis>&mccge-series; only</emphasis>: added in MySQL 5.1.16-ndb-6.2.0)</entry> + (<emphasis>&mccge-series; only</emphasis>: added in + MySQL 5.1.16-ndb-6.2.0)</entry> <entry>true|false (<literal>1</literal>|<literal>0</literal>)</entry> <entry>1</entry> <entry>0</entry> @@ -8563,9 +8567,10 @@ </para> <para> - For information about upgrading or downgrading between &mccge-series; releases, - or between &mccge-series; releases and mainline MySQL releases, see the changelogs - relating to &mccge-series;. + For information about upgrading or downgrading between + &mccge-series; releases, or between &mccge-series; releases and + mainline MySQL releases, see the changelogs relating to + &mccge-series;. </para> <para> @@ -13825,8 +13830,8 @@ <row> <entry><option>--skip-table-check</option></entry> <entry><option>-s</option></entry> - <entry>Do not check table schemas (Added in MySQL 5.1.17; - <emphasis>not supported in &mccge-series;</emphasis>)</entry> + <entry>Do not check table schemas (Added in MySQL 5.1.17; <emphasis>not + supported in &mccge-series;</emphasis>)</entry> <entry><literal>FALSE</literal></entry> </row> <row> @@ -14408,7 +14413,7 @@ </itemizedlist> - <!-- MERGED THROUGH HERE --> +<!-- MERGED THROUGH HERE --> <para> Most of these utilities need to connect to a Cluster management @@ -14440,7 +14445,8 @@ <listitem> <para> - <command>ndbd_redo_log_reader</command> (<emphasis>&mccge-series; only</emphasis>) + <command>ndbd_redo_log_reader</command> + (<emphasis>&mccge-series; only</emphasis>) </para> </listitem> @@ -19299,12 +19305,13 @@ <literal>NDB</literal> and <literal>NDBCLUSTER</literal>. </para> - <important> - <para> - In MySQL 5.1.8 and later, there can exist only one log - file group at any given time. - </para> - </important> + + <important> + <para> + In MySQL 5.1.8 and later, there can exist only one log + file group at any given time. + </para> + </important> </listitem> <listitem> @@ -20720,19 +20727,20 @@ </indexterm> <para> - In this section, we provide a list of known limitations in MySQL ¤t-series; - Cluster and &mccge-series; releases as compared with the - features available when using the <literal>MyISAM</literal> and - <literal>InnoDB</literal> storage engines. Currently, there are no - plans to address these in coming releases of MySQL - ¤t-series; or &mccge-series;; however, we will attempt to supply fixes for - these issues in subsequent release series. If you check the - <quote>Cluster</quote> category in the MySQL bugs database at + In this section, we provide a list of known limitations in MySQL + ¤t-series; Cluster and &mccge-series; releases as compared + with the features available when using the + <literal>MyISAM</literal> and <literal>InnoDB</literal> storage + engines. Currently, there are no plans to address these in coming + releases of MySQL ¤t-series; or &mccge-series;; however, we + will attempt to supply fixes for these issues in subsequent + release series. If you check the <quote>Cluster</quote> category + in the MySQL bugs database at <ulink url="http://bugs.mysql.com"/>, you can find known bugs which (if marked <quote>¤t-series;</quote>) we intend to - correct in upcoming releases of MySQL ¤t-series;. Some of these issues - may be addressed in &mccge-series; and the fixes included in a future - mainline MySQL Cluster version. + correct in upcoming releases of MySQL ¤t-series;. Some of + these issues may be addressed in &mccge-series; and the fixes + included in a future mainline MySQL Cluster version. </para> <para> @@ -21634,8 +21642,8 @@ <para> We may support multiple data nodes per host in a future MySQL release, following additional testing. However, in - MySQL ¤t-series; and &mccge-series;, such configurations can be - considered experimental only. + MySQL ¤t-series; and &mccge-series;, such + configurations can be considered experimental only. </para> </listitem> @@ -21787,8 +21795,9 @@ <listitem> <para> - The maximum number of metadata objects in MySQL ¤t-series; - Cluster and &mccge-series; is 20320. This limit is hard-coded. + The maximum number of metadata objects in MySQL + ¤t-series; Cluster and &mccge-series; is 20320. This + limit is hard-coded. </para> </listitem> @@ -21981,8 +21990,8 @@ <para> In this section, we discuss changes in the implementation of MySQL - Cluster in MySQL ¤t-series; and &mccge-series; as compared to MySQL - &previous-series;. + Cluster in MySQL ¤t-series; and &mccge-series; as compared + to MySQL &previous-series;. <!-- We also discuss our roadmap for further improvements to MySQL Cluster
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r6267 - trunk/refman-5.1 | jon | 30 Apr |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.535 sec. using MySQL 5.1.14-beta-log