svn commit - mysqldoc@docsrva: r11555 - in trunk: . dynamic-docs/changelog refman-6.0

[paul.dubois]

Author: paul
Date: 2008-08-14 06:13:42 +0200 (Thu, 14 Aug 2008)
New Revision: 11555

Log:
 r33353@frost:  paul | 2008-08-13 22:58:37 -0500
 Document bugfixes:
 Bug#31605: mysql_upgrade relies on Linux /proc filesystem when not running on Windows
 Bug#33002: Event Scheduler: Unnecessarily disabled after 5.1 -> 6.0.4 upgrade
 Bug#33053: mysql_upgrade: Does not convert all mysql db tables from utf8mb3 to utf8
 Bug#35808: utf8 hungarian collation not part of the utf8 charset?
 Bug#37662: nested if() inside sum() is parsed in exponential time
 Bug#38002: table_cache consumes too much memory with blobs


Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/refman-6.0/installing-core.xml
   trunk/refman-6.0/internationalization.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:33348
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32725
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:33353
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32725


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-08-13 23:00:19 UTC (rev 11554)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-08-14 04:13:42 UTC (rev 11555)
Changed blocks: 2, Lines Added: 160, Lines Deleted: 5; 4504 bytes

@@ -12264,11 +12264,13 @@
 
       <para>
         If you use events, a known issue is that if you upgrade from
-        MySQL 5.1 to 6.0.4, the event scheduler will not work, even
-        after you run <command>mysql_upgrade</command>. (This is an
-        issue only for an upgrade, not for a new installation of MySQL
-        6.0.4.) To work around this upgrading problem, use these
-        instructions:
+        MySQL 5.1 to 6.0.4 though 6.0.6, the event scheduler will not
+        work, even after you run <command>mysql_upgrade</command>. (This
+        is an issue only for an upgrade, not for a new installation of
+        MySQL 6.0.x.) As of MySQL 6.0.7,
+        <command>mysql_upgrade</command> handles upgrading the system
+        tables properly. If you upgrade to 6.0.4 through 6.0.6, you can
+        work around this upgrading problem by using these instructions:
       </para>
 
       <orderedlist>

@@ -24490,4 +24492,157 @@
 
   </logentry>
 
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="mysql_upgrade"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="31605"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.68"/>
+      <version ver="5.1.28"/>
+      <version ver="6.0.7"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <command>mysql_upgrade</command> attempted to use the
+        <filename>/proc</filename> filesystem even on systems that do
+        not have it.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="utf8"/>
+      <manual type="utf8mb3"/>
+      <manual type="mysql_upgrade"/>
+      <manual type="event scheduler"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="33002"/>
+      <fixes bugid="33053"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.7"/>
+    </versions>
+
+    <message>
+
+      <para>
+        After an upgrade to MySQL 6.0.4 or higher, columns that used the
+        old 3-byte Unicode <literal>utf8</literal> character set are
+        treated as having the <literal>utf8mb3</literal> character set.
+        <command>mysql_upgrade</command> did not convert all system
+        tables in the <literal>mysql</literal> database to use the new
+        4-byte Unicode <literal>utf8</literal> character set rather than
+        <literal>utf8mb3</literal>. This caused problems such as that
+        the event scheduler would not start.
+        <command>mysql_upgrade</command> now performs the
+        <literal>utf8mb3</literal> to <literal>utf8</literal>
conversion
+        for system tables.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="utf8"/>
+      <manual type="utf8_hungarian_ci"/>
+      <manual type="configure"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="35808"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.28"/>
+      <version ver="6.0.7"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <command>configure</command> script did not allow
+        <literal>utf8_hungarian_ci</literal> to be specified as the
+        default collation.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="IF()"/>
+      <manual type="SUM()"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="37662"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.68"/>
+      <version ver="5.1.28"/>
+      <version ver="6.0.7"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Nesting of <function role="sql">IF()</function> inside of
+        <function role="sql">SUM()</function> could cause an extreme
+        server slowdown.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="table definition cache"/>
+      <manual type="BLOB"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="38002"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.28"/>
+      <version ver="6.0.7"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If the table definition cache contained tables with many
+        <literal>BLOB</literal> columns, much memory could be allocated
+        to caching <literal>BLOB</literal> values. Now a size limit on
+        the cached <literal>BLOB</literal> values is enforced.
+      </para>
+
+    </message>
+
+  </logentry>
+
 </changelog>


Modified: trunk/refman-6.0/installing-core.xml
===================================================================
--- trunk/refman-6.0/installing-core.xml	2008-08-13 23:00:19 UTC (rev 11554)
+++ trunk/refman-6.0/installing-core.xml	2008-08-14 04:13:42 UTC (rev 11555)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 5; 1247 bytes

@@ -12867,11 +12867,14 @@
 
           <para>
             If you use events, a known issue is that if you upgrade from
-            MySQL 5.1 to 6.0.4, the event scheduler will not work, even
-            after you run <command>mysql_upgrade</command>. (This is an
-            issue only for an upgrade, not for a new installation of
-            MySQL 6.0.4.) To work around this upgrading problem, use
-            these instructions:
+            MySQL 5.1 to 6.0.4 though 6.0.6, the event scheduler will
+            not work, even after you run
+            <command>mysql_upgrade</command>. (This is an issue only for
+            an upgrade, not for a new installation of MySQL 6.0.x.) As
+            of MySQL 6.0.7, <command>mysql_upgrade</command> handles
+            upgrading the system tables properly. If you upgrade to
+            6.0.4 through 6.0.6, you can work around this upgrading
+            problem by using these instructions:
           </para>
 
           <orderedlist>


Modified: trunk/refman-6.0/internationalization.xml
===================================================================
--- trunk/refman-6.0/internationalization.xml	2008-08-13 23:00:19 UTC (rev 11554)
+++ trunk/refman-6.0/internationalization.xml	2008-08-14 04:13:42 UTC (rev 11555)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 5; 1184 bytes

@@ -3481,11 +3481,13 @@
 
       <para>
         If you use events, a known issue is that if you upgrade from
-        MySQL 5.1 to 6.0.4, the event scheduler will not work, even
-        after you run <command>mysql_upgrade</command>. (This is an
-        issue only for an upgrade, not for a new installation of MySQL
-        6.0.4.) To work around this upgrading problem, use these
-        instructions:
+        MySQL 5.1 to 6.0.4 though 6.0.6, the event scheduler will not
+        work, even after you run <command>mysql_upgrade</command>. (This
+        is an issue only for an upgrade, not for a new installation of
+        MySQL 6.0.x.) As of MySQL 6.0.7,
+        <command>mysql_upgrade</command> handles upgrading the system
+        tables properly. If you upgrade to 6.0.4 through 6.0.6, you can
+        work around this upgrading problem by using these instructions:
       </para>
 
       <orderedlist>