Author: paul
Date: 2006-04-28 15:17:02 +0200 (Fri, 28 Apr 2006)
New Revision: 1965
Log:
r9874@frost: paul | 2006-04-28 08:13:47 -0500
mysql_upgrade is no longer Unix-only. (Bug#18115)
Modified:
trunk/
trunk/refman-5.0/database-administration.xml
trunk/refman-5.0/installing.xml
trunk/refman-5.1/database-administration.xml
trunk/refman-5.1/installing.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:7031
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9830
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4590
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:7031
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9874
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4590
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2006-04-28 11:13:26 UTC (rev 1964)
+++ trunk/refman-5.0/database-administration.xml 2006-04-28 13:17:02 UTC (rev 1965)
@@ -5338,28 +5338,28 @@
connections over named pipes.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_autoincrement_prefetch_sz</literal>
</para>
-
+
<para>
Determines the probability of gaps in an autoincremented
column. Set to <literal>1</literal> to minimize this. Set
to a high value for optimization — makes inserts
faster, but decreases the likelihood that consecutive
- autoincrement numbers will be used in a batch of
- inserts. Default value: <literal>32</literal>. Mimimum
- value: <literal>1</literal>.
+ autoincrement numbers will be used in a batch of inserts.
+ Default value: <literal>32</literal>. Mimimum value:
+ <literal>1</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>ndb_cache_check_time</literal>
+ <literal>ndb_cache_check_time</literal>
</para>
-
+
<para>
The number of seconds to wait before checking the
<literal>NDB</literal> query cache. Setting this to
@@ -5369,27 +5369,27 @@
means the <literal>NDB</literal> query cache will seldom
be checked and invalidated because of updates on another
<command>mysqld</command>. It is generally not desirable
- to set this to a value greater than <literal>2</literal>.
+ to set this to a value greater than <literal>2</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_force_send</literal>
</para>
-
+
<para>
Forces sending of buffers to <literal>NDB</literal>
immediately, without waiting for other threads. Defaults
to <literal>ON</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_index_stat_cache_entries</literal>
</para>
-
+
<para>
Sets the granularity of the statistics by determining the
number of starting and ending keys to store in the
@@ -5398,23 +5398,23 @@
directly. Default value: <literal>32</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>ndb_index_stat_enable</literal>
+ <literal>ndb_index_stat_enable</literal>
</para>
-
+
<para>
Use <literal>NDB</literal> index statistics in query
optimization. Defaults to <literal>ON</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_index_stat_update_freq</literal>
</para>
-
+
<para>
How often to query data nodes instead of the statistics
cache. For example, a value of <literal>20</literal> (the
@@ -5422,12 +5422,12 @@
20<superscript>th</superscript> query to the data nodes.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_report_thresh_binlog_epoch_slip</literal>
</para>
-
+
<para>
This is a threshold on the number of epochs to be behind
before reporting binlog status. For example, a value of
@@ -5438,12 +5438,12 @@
cluster log.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_report_thresh_binlog_mem_usage</literal>
</para>
-
+
<para>
This is a threshold on the percentage of free memory
remaining before reporting binlog status. For example, a
@@ -5453,12 +5453,12 @@
be sent to the cluster log.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_use_exact_count</literal>
</para>
-
+
<para>
Forces <literal>NDB</literal> to use an count of records
during <literal>SELECT COUNT(*)</literal> query planning
@@ -5469,17 +5469,17 @@
<literal>OFF</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_use_transactions</literal>
</para>
-
+
<para>
You can disable <literal>NDB</literal> transaction support
by setting this variable's values to
<literal>OFF</literal> (not recommended). The default is
- <literal>ON</literal>.
+ <literal>ON</literal>.
</para>
</listitem>
@@ -13796,11 +13796,16 @@
</programlisting>
<para>
- <command>mysql_upgrade</command> currently works only on
- Unix. On Windows, you can execute the
- <command>mysqlcheck</command> command manually, and then
- upgrade your system tables as described in
- <xref linkend="mysql-fix-privilege-tables"/>.
+ <command>mysql_upgrade</command> supersedes the older
+ <command>mysql_fix_privilege_tables</command> script. In
+ MySQL 5.0.19, <command>mysql_upgrade </command> was added as
+ a shell script and worked only for Unix systems. As of MySQL
+ 5.0.22, <command>mysql_upgrade</command> is an executable
+ binary and is available on all systems. On systems older
+ than those supporting <command>mysql_upgrade</command>, you
+ can execute the <command>mysqlcheck</command> command
+ manually, and then upgrade your system tables as described
+ in <xref linkend="mysql-fix-privilege-tables"/>.
</para>
<para>
@@ -13966,12 +13971,6 @@
option.
</para>
- <para>
- <command>mysql_upgrade</command> was added in MySQL 5.0.19.
- It supersedes the older
- <command>mysql_fix_privilege_tables</command> script.
- </para>
-
</refsection>
</refentry>
Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2006-04-28 11:13:26 UTC (rev 1964)
+++ trunk/refman-5.0/installing.xml 2006-04-28 13:17:02 UTC (rev 1965)
@@ -11682,10 +11682,11 @@
<para>
To avoid problems due to such changes, after you upgrade to a
- new version of MySQL, you should check your tables (and repair
- them if necessary), and update your grant tables to make sure
- that they have the current structure so that you can take
- advantage of any new capabilities. See
+ new version of MySQL, you should run
+ <command>mysql_upgrade</command> to check your tables (and
+ repair them if necessary), and to update your grant tables to
+ make sure that they have the current structure so that you can
+ take advantage of any new capabilities. See
<xref linkend="mysql-upgrade"/>.
</para>
</listitem>
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2006-04-28 11:13:26 UTC (rev 1964)
+++ trunk/refman-5.1/database-administration.xml 2006-04-28 13:17:02 UTC (rev 1965)
@@ -5678,28 +5678,28 @@
connections over named pipes.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_autoincrement_prefetch_sz</literal>
</para>
-
+
<para>
Determines the probability of gaps in an autoincremented
column. Set to <literal>1</literal> to minimize this. Set
to a high value for optimization — makes inserts
faster, but decreases the likelihood that consecutive
- autoincrement numbers will be used in a batch of
- inserts. Default value: <literal>32</literal>. Mimimum
- value: <literal>1</literal>.
+ autoincrement numbers will be used in a batch of inserts.
+ Default value: <literal>32</literal>. Mimimum value:
+ <literal>1</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>ndb_cache_check_time</literal>
+ <literal>ndb_cache_check_time</literal>
</para>
-
+
<para>
The number of seconds to wait before checking the
<literal>NDB</literal> query cache. Setting this to
@@ -5709,7 +5709,7 @@
means the <literal>NDB</literal> query cache will seldom
be checked and invalidated because of updates on another
<command>mysqld</command>. It is generally not desirable
- to set this to a value greater than <literal>2</literal>.
+ to set this to a value greater than <literal>2</literal>.
</para>
</listitem>
@@ -5724,29 +5724,29 @@
troubleshooting purposes. The default value is
<literal>0</literal>.
</para>
-
+
<para>
This variable was added in MySQL 5.1.6.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_force_send</literal>
</para>
-
+
<para>
Forces sending of buffers to <literal>NDB</literal>
immediately, without waiting for other threads. Defaults
to <literal>ON</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_index_stat_cache_entries</literal>
</para>
-
+
<para>
Sets the granularity of the statistics by determining the
number of starting and ending keys to store in the
@@ -5755,23 +5755,23 @@
directly. Default value: <literal>32</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>ndb_index_stat_enable</literal>
+ <literal>ndb_index_stat_enable</literal>
</para>
-
+
<para>
Use <literal>NDB</literal> index statistics in query
optimization. Defaults to <literal>ON</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_index_stat_update_freq</literal>
</para>
-
+
<para>
How often to query data nodes instead of the statistics
cache. For example, a value of <literal>20</literal> (the
@@ -5779,12 +5779,12 @@
20<superscript>th</superscript> query to the data nodes.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_report_thresh_binlog_epoch_slip</literal>
</para>
-
+
<para>
This is a threshold on the number of epochs to be behind
before reporting binlog status. For example, a value of
@@ -5795,12 +5795,12 @@
cluster log.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_report_thresh_binlog_mem_usage</literal>
</para>
-
+
<para>
This is a threshold on the percentage of free memory
remaining before reporting binlog status. For example, a
@@ -5810,12 +5810,12 @@
be sent to the cluster log.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_use_exact_count</literal>
</para>
-
+
<para>
Forces <literal>NDB</literal> to use an count of records
during <literal>SELECT COUNT(*)</literal> query planning
@@ -5826,19 +5826,19 @@
<literal>OFF</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ndb_use_transactions</literal>
</para>
-
+
<para>
You can disable <literal>NDB</literal> transaction support
by setting this variable's values to
<literal>OFF</literal> (not recommended). The default is
- <literal>ON</literal>.
+ <literal>ON</literal>.
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
@@ -13721,8 +13721,14 @@
</programlisting>
<para>
- <command>mysql_upgrade</command> currently works only on
- Unix. On Windows, you can execute the
+ <command>mysql_upgrade</command> supersedes the
+ older <command>mysql_fix_privilege_tables</command> script.
+ In MySQL 5.1.7, <command>mysql_upgrade </command> was added
+ as a shell script and worked only for Unix systems. As of
+ MySQL 5.1.10, <command>mysql_upgrade</command> is an
+ executable binary and is available on all systems. On
+ systems older than those supporting
+ <command>mysql_upgrade</command>, you can execute the
<command>mysqlcheck</command> command manually, and then
upgrade your system tables as described in
<xref linkend="mysql-fix-privilege-tables"/>.
@@ -13891,12 +13897,6 @@
option.
</para>
- <para>
- <command>mysql_upgrade</command> was added in MySQL 5.1.7.
- It supersedes the older
- <command>mysql_fix_privilege_tables</command> script.
- </para>
-
</refsection>
</refentry>
Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml 2006-04-28 11:13:26 UTC (rev 1964)
+++ trunk/refman-5.1/installing.xml 2006-04-28 13:17:02 UTC (rev 1965)
@@ -11802,10 +11802,11 @@
<para>
To avoid problems due to such changes, after you upgrade to
- a new version of MySQL, you should check your tables (and
- repair them if necessary), and update your grant tables to
- make sure that they have the current structure so that you
- can take advantage of any new capabilities. See
+ a new version of MySQL, you should run
+ <command>mysql_upgrade</command> to check your tables (and
+ repair them if necessary), and to update your grant tables
+ to make sure that they have the current structure so that
+ you can take advantage of any new capabilities. See
<xref linkend="mysql-upgrade"/>.
</para>
</listitem>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-04-28 11:13:26 UTC (rev 1964)
+++ trunk/refman-common/news-5.0.xml 2006-04-28 13:17:02 UTC (rev 1965)
@@ -194,7 +194,13 @@
<itemizedlist>
<listitem>
- <para></para>
+ <para>
+ The <command>mysql_upgrade</command> command has been
+ converted from a shell script to a C program, so it is
+ available on non-Unix systems such as Windows. This program
+ should be run for each MySQL upgrade. See
+ <xref linkend="mysql-upgrade"/>.
+ </para>
</listitem>
</itemizedlist>
@@ -204,28 +210,28 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Stopping multiple nodes could
cause node failure handling not to be completed. (Bug #19039)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <command>ndbd</command> could
sometimes fail to start with the error <errortext>Node failure
- handling not completed</errortext> following a graceful
+ handling not completed</errortext> following a graceful
restart. (Bug #18550)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Backups could fail for large
- clusters with many tables, where the number of tables approached
- <literal>MaxNoOfTables</literal>. (Bug #17607)
+ clusters with many tables, where the number of tables
+ approached <literal>MaxNoOfTables</literal>. (Bug #17607)
</para>
</listitem>
@@ -333,11 +339,11 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A simultaneous <literal>DROP
- TABLE</literal> and table update operation utilising a table
+ TABLE</literal> and table update operation utilising a table
scan could trigger a node failure. (Bug #18597)
</para>
</listitem>
@@ -1495,17 +1501,56 @@
<literal>VARBINARY</literal> types.
</para>
</listitem>
-
+
<listitem>
<para>
+ Several changes were made to make upgrades easier:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Added the <command>mysql_upgrade</command> program that
+ checks all tables for incompatibilities with the current
+ version of MySQL Server and repairs them if necessary.
+ This program should be run for each MySQL upgrade (rather
+ than <command>mysql_fix_privilege_tables</command>). See
+ <xref linkend="mysql-upgrade"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Added the <literal>FOR UPGRADE</literal> option for the
+ <literal>CHECK TABLE</literal> statement. This option
+ checks whether tables are incompatible with the current
+ version of MySQL Server.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Added the <option>--check-upgrade</option> to
+ <command>mysqlcheck</command> that invokes <literal>CHECK
+ TABLE</literal> with the <literal>FOR UPGRADE</literal>
+ option.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: The <command>ndb_mgm</command>
client commands <literal><replaceable>node_id</replaceable>
- START</literal> and
+ START</literal> and
<literal><replaceable>node_id</replaceable> STOP</literal> now
work with management nodes as well as data nodes. (However,
using <literal>ALL</literal> for the
<replaceable>node_id</replaceable> continues to affect all
- data nodes only.)
+ data nodes only.)
</para>
</listitem>
@@ -1530,29 +1575,6 @@
<listitem>
<para>
- Added the <command>mysql_upgrade</command> program that checks
- all tables for incompatibilities with the current version of
- MySQL Server and repairs them if necessary. This program
- should be run for each MySQL upgrade (rather than
- <command>mysql_fix_privilege_tables</command>). See
- <xref linkend="mysql-upgrade"/>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Added the <literal>FOR UPGRADE</literal> option for the
- <literal>CHECK TABLE</literal> statement. This option checks
- whether tables are incompatible with the current version of
- MySQL Server. Also added the <option>--check-upgrade</option>
- to <command>mysqlcheck</command> that invokes <literal>CHECK
- TABLE</literal> with the <literal>FOR UPGRADE</literal>
- option.
- </para>
- </listitem>
-
- <listitem>
- <para>
<command>mysql</command> no longer terminates data value
display when it encounters a NUL byte. Instead, it displays
NUL bytes as spaces. (Bug #16859)
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-04-28 11:13:26 UTC (rev 1964)
+++ trunk/refman-common/news-5.1.xml 2006-04-28 13:17:02 UTC (rev 1965)
@@ -86,6 +86,16 @@
<listitem>
<para>
+ The <command>mysql_upgrade</command> command has been
+ converted from a shell script to a C program, so it is
+ available on non-Unix systems such as Windows. This program
+ should be run for each MySQL upgrade. See
+ <xref linkend="mysql-upgrade"/>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
On Windows, some names such as <literal>nul</literal>,
<literal>prn</literal>, and <literal>aux</literal> cannot be
used as filenames because they are reserved as device names.
@@ -157,46 +167,46 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Replication): When taking part
in Cluster replication of tables containing
<literal>BLOB</literal> columns, <command>mysqld</command>
falsely reported a large memory leak in the replication
- buffers when there was none. (Bug #19247)
+ buffers when there was none. (Bug #19247)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Stopping multiple nodes could
cause node failure handling not to be completed. (Bug #19039)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A simultaneous <literal>DROP
- TABLE</literal> and table update operation utilising a table
+ TABLE</literal> and table update operation utilising a table
scan could trigger a node failure. (Bug #18597)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <command>ndbd</command> could
sometimes fail to start with the error <errortext>Node failure
- handling not completed</errortext> following a graceful
+ handling not completed</errortext> following a graceful
restart. (Bug #18550)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Backups could fail for large
- clusters with many tables, where the number of tables approached
- <literal>MaxNoOfTables</literal>. (Bug #17607)
+ clusters with many tables, where the number of tables
+ approached <literal>MaxNoOfTables</literal>. (Bug #17607)
</para>
</listitem>
@@ -2607,7 +2617,7 @@
Added the <option>--check-upgrade</option> to
<command>mysqlcheck</command> that invokes <literal>CHECK
TABLE</literal> with the <literal>FOR UPGRADE</literal>
- Added the <option>--fix-db-names</option> and
+ option. Added the <option>--fix-db-names</option> and
<option>--fix-table-names</option> options to
<command>mysqlcheck</command>.
</para>
@@ -2753,7 +2763,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <command>ndbd</command>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1965 - in trunk: . refman-5.0 refman-5.1 refman-common | paul | 28 Apr |
