Author: paul
Date: 2006-04-11 05:43:51 +0200 (Tue, 11 Apr 2006)
New Revision: 1786
Log:
Modified:
trunk/
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:6548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9363
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9365
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-04-11 03:42:58 UTC (rev 1785)
+++ trunk/refman-common/news-5.0.xml 2006-04-11 03:43:51 UTC (rev 1786)
@@ -479,6 +479,53 @@
<listitem>
<para>
+ If <literal>InnoDB</literal> ran out of buffer space for row
+ locks and adaptive hashes, the server would crash. Now
+ <literal>InnoDB</literal> rolls back the transaction. (Bug
+ #18238)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> tables with an adaptive hash blocked
+ other queries during <literal>CHECK TABLE</literal> statements
+ while the entire hash was checked. This could be a long time
+ for a large hash. (Bug #17126)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>InnoDB</literal> tables created in MySQL 4.1 or
+ earlier, or created in 5.0 or later with compact format,
+ updating a row so that a long column is updated or the length
+ of some column changes, <literal>InnoDB</literal> later would
+ fail to reclaim the <literal>BLOB</literal> storage space if
+ the row was deleted. (Bug #18252)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> had a memory leak for duplicate-key
+ errors with tables having 90 columns or more. (Bug #18384)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Checks for permissions on database operations could be
+ performed in a case-insensitive manner (a user with
+ permissions on database <literal>MYDATABASE</literal> could by
+ accident get permissions on database
+ <literal>myDataBase</literal>), if the privilege data were
+ still cached from a previous check. (Bug #17279)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>InnoDB</literal>: The <literal>LATEST FOREIGN KEY
ERROR</literal> section in the output of <literal>SHOW INNODB
STATUS</literal> was sometimes formatted incorrectly, causing
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-04-11 03:42:58 UTC (rev 1785)
+++ trunk/refman-common/news-5.1.xml 2006-04-11 03:43:51 UTC (rev 1786)
@@ -862,6 +862,17 @@
<listitem>
<para>
+ Checks for permissions on database operations could be
+ performed in a case-insensitive manner (a user with
+ permissions on database <literal>MYDATABASE</literal> could by
+ accident get permissions on database
+ <literal>myDataBase</literal>), if the privilege data were
+ still cached from a previous check. (Bug #17279)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The server would crash when <literal>SHOW STATUS</literal> was
called on a server linked with <literal>yaSSL</literal>. (Bug
#18310)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1786 - in trunk: . refman-common | paul | 11 Apr |
