MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon Date:November 20 2007 10:28am
Subject:svn commit - mysqldoc@docsrva: r8793 - trunk/dynamic-docs/changelog
View as plain text  
Author: jstephens
Date: 2007-11-20 11:28:39 +0100 (Tue, 20 Nov 2007)
New Revision: 8793

Log:


Consolidated more duplicate changelog entries



Modified:
   trunk/dynamic-docs/changelog/dupes.txt
   trunk/dynamic-docs/changelog/mysqld.xml


Modified: trunk/dynamic-docs/changelog/dupes.txt
===================================================================
--- trunk/dynamic-docs/changelog/dupes.txt	2007-11-20 07:57:47 UTC (rev 8792)
+++ trunk/dynamic-docs/changelog/dupes.txt	2007-11-20 10:28:39 UTC (rev 8793)
Changed blocks: 1, Lines Added: 25, Lines Deleted: 25; 654 bytes

@@ -323,31 +323,31 @@
 27998x
 28023x
 28073x
-28093
-28161
-28181
-28276
-28348
-28423
-28430
-28443
-28525
-28570
-28642
-28653
-28717
-28719
-28720
-28724
-28726
-28749
-28751
-28770
-28783
-28804
-28899
-28949
-28984
+28093x
+28161x
+28181x
+28276x
+28348x
+28423x
+28430x
+28443x
+28525x
+28570x
+28642x
+28653x
+28717x
+28719x
+28720x
+28724x
+28726x
+28749x
+28751x
+28770x
+28783x
+28804x
+28899x
+28949x
+28984x
 29044
 29057
 29063


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2007-11-20 07:57:47 UTC (rev 8792)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2007-11-20 10:28:39 UTC (rev 8793)
Changed blocks: 62, Lines Added: 97, Lines Deleted: 699; 26498 bytes

@@ -8813,58 +8813,6 @@
     </tags>
 
     <bugs>
-      <fixes bugid="28726"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.20"/>
-    </versions>
-
-    <message>
-
-      <para>
-        LCP files were not removed following an initial system restart.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="COPY_GCIREQ"/>
-      <manual type="NODE_FAILREP"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28717"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.10"/>
-      <version ver="5.1.19-ndb-6.2.3"/>
-    </versions>
-
-    <message>
-
-      <para>
-        A race condition could occur between
-        <literal>NODE_FAILREP</literal> and
-        <literal>COPY_GCIREQ</literal> events.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <highlight type="cluster"/>
-    </tags>
-
-    <bugs>
       <fixes bugid="20904"/>
     </bugs>
 

@@ -12329,6 +12277,8 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="replication"/>
+      <highlight type="partitioning"/>
       <manual type="replication"/>
       <manual type="partitioning"/>
       <manual type="InnoDB"/>

@@ -12339,7 +12289,7 @@
     </bugs>
 
     <versions>
-      <version ver="5.1.21"/>
+      <version ver="5.1.23"/>
     </versions>
 
     <message>

@@ -12545,6 +12495,8 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.11"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 

@@ -17107,6 +17059,7 @@
       <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="mysqld"/>
+      <manual type="binlog"/>
     </tags>
 
     <bugs>

@@ -17114,6 +17067,7 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 

@@ -22484,6 +22438,7 @@
     <versions>
       <version ver="5.0.42"/>
       <version ver="5.0.45"/>
+      <version ver="5.1.15-ndb-6.1.7"/>
       <version ver="5.1.18"/>
     </versions>
 

@@ -27278,19 +27233,22 @@
     </bugs>
 
     <versions>
-      <version ver="5.0.45"/>
       <version ver="5.0.44"/>
+      <version ver="5.0.45"/>
+      <version ver="5.1.15-ndb-6.1.10"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 
     <message>
 
       <para>
-        The actual value of <literal>MaxNoOfOpenFiles</literal> as used
-        by the cluster was offset by 1 from the value set in
-        <filename>config.ini</filename>. This meant that setting
-        <literal>InitialNoOpenFiles</literal>to the same value always
-        caused an error.
+        Setting <literal>InitialNoOpenFiles</literal> equal to
+        <literal>MaxNoOfOpenFiles</literal> caused an error. This was
+        due to the fact that the actual value of
+        <literal>MaxNoOfOpenFiles</literal> as used by the cluster was
+        offset by 1 from the value set in
+        <filename>config.ini</filename>.
       </para>
 
     </message>

@@ -27822,33 +27780,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <manual type="cluster"/>
-      <manual type="mysqld"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28949"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.19-ndb-6.2.3"/>
-    </versions>
-
-    <message>
-
-      <para>
-        When shutting down <command>mysqld</command>, the
-        <literal>NDB</literal> binlog process was not shut down before
-        log cleanup began.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <highlight type="cluster"/>
       <manual type="cluster"/>
       <manual type="SHOW"/>

@@ -28252,31 +28183,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28642"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.21"/>
-    </versions>
-
-    <message>
-
-      <para>
-        (Disk Data): The number of free extents was incorrectly reported
-        for some tablespaces.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="UNION"/>
       <manual type="DECIMAL"/>
     </tags>

@@ -29892,33 +29798,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
-      <manual type="BLOB"/>
-      <manual type="transactions"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28724"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.20"/>
-    </versions>
-
-    <message>
-
-      <para>
-        (APIs): An invalid error code could be set on transaction
-        objects by <literal>BLOB</literal> handling code.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="MaxAllocate"/>
     </tags>
 

@@ -31926,6 +31805,8 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.11"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 

@@ -35834,31 +35715,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <manual type="cluster"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28423"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.22-ndb-6.2.6"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Mapping of <literal>NDB</literal> error codes to storage engine
-        error codes has been improved.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="replication"/>
       <manual type="Slave_open_temp_tables"/>
       <manual type="TEMPORARY"/>

@@ -36604,33 +36460,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
-      <manual type="cluster"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28443"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.19-ndb-6.2.3"/>
-      <version ver="5.1.15-ndb-6.1.9"/>
-    </versions>
-
-    <message>
-
-      <para>
-        The <literal>NDB</literal> transporter would hang when more than
-        1024 signals were received at one time.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="Windows"/>
       <manual type="LOCK TABLES"/>
       <manual type="MyISAM"/>

@@ -39719,10 +39548,12 @@
 
       <para>
         Non-range queries of the form <literal>SELECT ... FROM ... WHERE
-        keypart_1=const, ..., keypart_n=const ORDER BY ... FOR
-        UPDATE</literal> sometimes were unnecessarily blocked waiting
-        for a lock if another transaction was using <literal>SELECT ...
-        FOR UPDATE</literal> on the same table.
+        <replaceable>keypart1</replaceable>=<replaceable>constant</replaceable>,
+        ...,
+        <replaceable>keypartN</replaceable>=<replaceable>constant</replaceable>
+        ORDER BY ... FOR UPDATE</literal> sometimes were unnecessarily
+        blocked waiting for a lock if another transaction was using
+        <literal>SELECT ... FOR UPDATE</literal> on the same table.
       </para>
 
     </message>

@@ -41225,7 +41056,9 @@
     </bugs>
 
     <versions>
+      <version ver="5.0.50"/>
       <version ver="5.1.22-ndb-6.2.5"/>
+      <version ver="5.1.23"/>
     </versions>
 
     <message>

@@ -41249,7 +41082,6 @@
 
     <tags>
       <highlight type="cluster"/>
-      <highlight type="clusterreplication"/>
       <manual type="replication"/>
       <manual type="cluster"/>
     </tags>

@@ -41259,6 +41091,7 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.18-ndb-6.2.1"/>
       <version ver="5.1.19"/>
     </versions>
 

@@ -45126,35 +44959,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="diskdata"/>
-      <manual type="ndbd"/>
-      <manual type="mysqld"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28720"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.18"/>
-      <version ver="5.1.19-ndb-6.2.4"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Disk data meta-information that existed in
-        <command>ndbd</command> was not always visible to
-        <command>mysqld</command>.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="UNION"/>
       <manual type="EXPLAIN"/>
     </tags>

@@ -45501,40 +45305,7 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
       <manual type="replication"/>
-      <manual type="cluster"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28276"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.18-ndb-6.2.1"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Multiple operations involving deletes followed by reads were not
-        handled correctly.
-      </para>
-
-      <note>
-        <para>
-          This issue could also affect MySQL Cluster Replication.
-        </para>
-      </note>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="replication"/>
       <manual type="Query"/>
       <manual type="Intvar"/>
       <manual type="transactions"/>

@@ -47334,40 +47105,7 @@
 
   <logentry entrytype="bug">
 
-    <tags>
-      <highlight type="cluster"/>
-      <manual type="cluster"/>
-      <manual type="MaxNoOfOpenFiles"/>
-      <manual type="InitialNoOpenFiles"/>
-      <manual type="config.ini"/>
-    </tags>
-
     <bugs>
-      <fixes bugid="28749"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.10"/>
-      <version ver="5.1.19-ndb-6.2.3"/>
-    </versions>
-
-    <message>
-
-      <para>
-        The actual value of <literal>MaxNoOfOpenFiles</literal> as used
-        by the cluster was offset by 1 from the value set in
-        <filename>config.ini</filename>. This meant that setting
-        <literal>InitialNoOpenFiles</literal>to the same value always
-        caused an error.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <bugs>
       <fixes bugid="18930"/>
     </bugs>
 

@@ -48120,14 +47858,15 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.8"/>
       <version ver="5.1.19"/>
     </versions>
 
     <message>
 
       <para>
-        Local checkpoint files related to dropped <literal>NDB</literal>
-        tables were not removed.
+        Local checkpoint files relating to dropped
+        <literal>NDB</literal> tables were not removed.
       </para>
 
     </message>

@@ -48705,14 +48444,17 @@
     </bugs>
 
     <versions>
-      <version ver="5.0.45"/>
       <version ver="5.0.44"/>
+      <version ver="5.0.45"/>
+      <version ver="5.1.15-ndb-6.1.10"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
+      <version ver="5.1.20"/>
     </versions>
 
     <message>
 
       <para>
-        : A corrupt schema file could cause a <errortext>File already
+        A corrupt schema file could cause a <errortext>File already
         open</errortext> error.
       </para>
 

@@ -52962,8 +52704,9 @@
     </bugs>
 
     <versions>
-      <version ver="5.1.19-ndb-6.2.4"/>
       <version ver="5.1.15-ndb-6.1.18"/>
+      <version ver="5.1.19-ndb-6.2.4"/>
+      <version ver="5.1.21"/>
     </versions>
 
     <message>

@@ -53827,15 +53570,16 @@
     </bugs>
 
     <versions>
-      <version ver="5.1.23"/>
       <version ver="5.0.50"/>
+      <version ver="5.1.22-ndb-6.2.6"/>
+      <version ver="5.1.23"/>
     </versions>
 
     <message>
 
       <para>
-        Mapping of <literal>NDB</literal> error codes to storage engine
-        error codes has been improved.
+        Mapping of <literal>NDB</literal> error codes to MySQL storage
+        engine error codes has been improved.
       </para>
 
     </message>

@@ -55917,6 +55661,7 @@
 
     <versions>
       <version ver="5.1.19-ndb-6.2.3"/>
+      <version ver="5.1.20"/>
     </versions>
 
     <message>

@@ -59923,26 +59668,6 @@
   <logentry entrytype="bug">
 
     <bugs>
-      <fixes bugid="28783"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.10"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Heartbeat failures could occur under high load.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <bugs>
       <fixes bugid="27406"/>
     </bugs>
 

@@ -61531,13 +61256,18 @@
 
   <logentry entrytype="bug">
 
+    <tags>
+      <highlight type="cluster"/>
+    </tags>
+
     <bugs>
       <fixes bugid="28726"/>
     </bugs>
 
     <versions>
-      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.15-ndb-6.1.11"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
+      <version ver="5.1.20"/>
     </versions>
 
     <message>

@@ -64346,6 +64076,7 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.10"/>
       <version ver="5.1.20"/>
     </versions>
 

@@ -64353,7 +64084,8 @@
 
       <para>
         A regression in the heartbeat monitoring code could lead to node
-        failure under high load. This issue affected MySQL 5.1.19 only.
+        failure under high load. This issue affected MySQL 5.1.19 and
+        MySQL 5.1.15-ndb-6.1.10 only.
       </para>
 
     </message>

@@ -64532,6 +64264,8 @@
 
     <tags>
       <highlight type="cluster"/>
+      <manual type="COPY_GCIREQ"/>
+      <manual type="NODE_FAILREP"/>
     </tags>
 
     <bugs>

@@ -64539,8 +64273,10 @@
     </bugs>
 
     <versions>
-      <version ver="5.0.45"/>
       <version ver="5.0.44"/>
+      <version ver="5.0.45"/>
+      <version ver="5.1.15-ndb-6.1.10"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 

@@ -64549,7 +64285,9 @@
       <para>
         A race condition could result when non-master nodes (in addition
         to the master node) tried to update active status due to a local
-        checkpoint. Now only the master updates the active status.
+        checkpoint (that is, between <literal>NODE_FAILREP</literal> and
+        <literal>COPY_GCIREQ</literal> events). Now only the master
+        updates the active status.
       </para>
 
     </message>

@@ -64773,28 +64511,6 @@
 
   <logentry entrytype="bug">
 
-    <bugs>
-      <fixes bugid="28770"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.10"/>
-      <version ver="5.1.19-ndb-6.2.3"/>
-    </versions>
-
-    <message>
-
-      <para>
-        A corrupt schema file could cause a <errortext>File already
-        open</errortext> error.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
     <tags>
       <manual type="binary log"/>
       <manual type="MIXED"/>

@@ -66592,28 +66308,6 @@
 
   <logentry entrytype="bug">
 
-    <bugs>
-      <fixes bugid="28653"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.10"/>
-      <version ver="5.1.19-ndb-6.2.3"/>
-    </versions>
-
-    <message>
-
-      <para>
-        A fast global checkpoint under high load with a high usage of
-        the redo buffer caused data nodes to fail.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
     <tags>
       <manual type="DELETE"/>
       <manual type="triggers"/>

@@ -67005,32 +66699,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
-      <manual type="cluster"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28348"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.8"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Local checkpoint files related to dropped <literal>NDB</literal>
-        tables were not removed.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="time_zone"/>
       <manual type="CONVERT_TZ"/>
     </tags>

@@ -67046,11 +66714,11 @@
     <message>
 
       <para>
-        Fixed bug which caused MySQL to require privileges on system
-        time zone description tables for implicit access to them (that
-        is, if one set <literal>time_zone</literal> variable or used
-        <literal>CONVERT_TZ()</literal> function) in case when some
-        table-level or column-level privileges existed.
+        MySQL required explicit privileges on system time zone
+        description tables for implicit access to them (that is, if one
+        set the <literal>time_zone</literal> variable or used the
+        <literal>CONVERT_TZ()</literal> function) in cases where some
+        table-level or column-level privileges already existed.
       </para>
 
     </message>

@@ -69621,7 +69289,8 @@
     </tags>
 
     <bugs>
-      <fixes bugid="28570"/>
+      <fixes bugid="29963"/>
+      <seealsobug bugid="26162"/>
     </bugs>
 
     <versions>

@@ -71050,33 +70719,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="diskdata"/>
-      <highlight type="clusterreplication"/>
-      <manual type="replication"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28161"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.7"/>
-    </versions>
-
-    <message>
-
-      <para>
-        / An issue with replication of Disk Data tables could in some
-        cases lead to node failure.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="EXPLAIN"/>
     </tags>
 

@@ -74323,16 +73965,18 @@
     </bugs>
 
     <versions>
-      <version ver="5.0.45"/>
       <version ver="5.0.44"/>
+      <version ver="5.0.45"/>
+      <version ver="5.1.15-ndb-6.1.10"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 
     <message>
 
       <para>
-        A fast global checkpoint under high load with a high usage of
-        the redo buffer caused data nodes to fail.
+        A fast global checkpoint under high load with high usage of the
+        redo buffer caused data nodes to fail.
       </para>
 
     </message>

@@ -78964,41 +78608,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
-      <manual type="cluster"/>
-      <manual type="TransactionBufferMemory"/>
-      <manual type="transactions"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28804"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.23"/>
-      <version ver="5.0.50"/>
-    </versions>
-
-    <message>
-
-      <para>
-        A query using joins between several large tables and requiring
-        unique index lookups failed to complete, eventually returning
-        <errortext>Uknown Error</errortext> after a very long period of
-        time. This occurred due to inadequate handling of instances
-        where the Transaction Coordinator ran out of
-        <literal>TransactionBufferMemory</literal>, when the cluster
-        should have returned NDB error code 4012 (<errortext>Request
-        ndbd time-out</errortext>).
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="SESSION_USER"/>
     </tags>
 

@@ -79193,6 +78802,8 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.18"/>
+      <version ver="5.1.19-ndb-6.2.4"/>
       <version ver="5.1.21"/>
     </versions>
 

@@ -85494,9 +85105,10 @@
     </bugs>
 
     <versions>
+      <version ver="4.1.24"/>
       <version ver="5.0.44"/>
+      <version ver="5.0.45"/>
       <version ver="5.1.20"/>
-      <version ver="4.1.24"/>
     </versions>
 
     <message>

@@ -85504,7 +85116,7 @@
       <para>
         A malformed password packet in the connection protocol could
         cause the server to crash. Thanks for Dormando for reporting
-        this bug and providing details and a proof of concept.
+        this bug, and for providing details and a proof of concept.
       </para>
 
     </message>

@@ -85606,6 +85218,7 @@
       <version ver="5.0.45"/>
       <version ver="5.0.44"/>
       <version ver="4.1.23"/>
+      <version ver="5.1.15-ndb-6.1.9"/>
       <version ver="5.1.19"/>
     </versions>
 

@@ -87519,36 +87132,6 @@
 
   </logentry>
 
-  <logentry entrytype="bug">
-
-    <tags>
-      <highlight type="cluster"/>
-      <manual type="ndbrequire"/>
-      <manual type="cluster"/>
-      <manual type="PGMAN"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28525"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.10"/>
-      <version ver="5.1.19-ndb-6.2.3"/>
-    </versions>
-
-    <message>
-
-      <para>
-        While loading data to the cluster after a version upgrade, data
-        nodes failed due to <literal>ndbrequire</literal> failures in
-        <literal>PGMAN</literal>.
-      </para>
-
-    </message>
-
-  </logentry>
-
   <logentry entrytype="feature">
 
     <tags>

@@ -88223,38 +87806,10 @@
   <logentry entrytype="bug">
 
     <tags>
-      <manual type="replication"/>
-      <manual type="partitioning"/>
       <manual type="InnoDB"/>
-      <manual type="row-based logging"/>
     </tags>
 
     <bugs>
-      <fixes bugid="28430"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.22"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Replication of <literal>InnoDB</literal> partitioned tables
-        could lose updates with row-based or mixed replication format.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="InnoDB"/>
-    </tags>
-
-    <bugs>
       <fixes bugid="19960"/>
     </bugs>
 

@@ -89625,31 +89180,6 @@
   <logentry entrytype="bug">
 
     <tags>
-      <highlight type="cluster"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28770"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.20"/>
-    </versions>
-
-    <message>
-
-      <para>
-        A corrupt schema file could cause a <errortext>File already
-        open</errortext> error.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <tags>
       <manual type="EVENT"/>
     </tags>
 

@@ -100666,27 +100196,10 @@
 
   <logentry entrytype="bug">
 
-    <bugs>
-      <fixes bugid="28751"/>
-    </bugs>
+    <tags>
+      <highlight type="partitioning"/>
+    </tags>
 
-    <versions>
-      <version ver="5.1.19-ndb-6.2.3"/>
-      <version ver="5.1.15-ndb-6.1.11"/>
-    </versions>
-
-    <message>
-
-      <para>
-        Having large amounts of memory locked caused swapping to disk.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
     <bugs>
       <fixes bugid="20770"/>
     </bugs>

@@ -102460,6 +101973,7 @@
 
     <bugs>
       <fixes bugid="26162"/>
+      <seealsobug bugid="29963"/>
     </bugs>
 
     <versions>

@@ -104057,6 +103571,7 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.7"/>
       <version ver="5.1.18"/>
     </versions>
 

@@ -106810,32 +106325,6 @@
 
   </logentry>
 
-  <logentry entrytype="bug">
-
-    <tags>
-      <highlight type="securityfix"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28984"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.0.45"/>
-    </versions>
-
-    <message>
-
-      <para>
-        A malformed password packet in the connection protocol could
-        cause the server to crash. Thanks for Dormando for reporting
-        this bug and providing details and a proof of concept.
-      </para>
-
-    </message>
-
-  </logentry>
-
   <logentry entrytype="feature">
 
     <tags>

@@ -111294,32 +110783,6 @@
 
   </logentry>
 
-  <logentry entrytype="bug">
-
-    <tags>
-      <highlight type="cluster"/>
-      <manual type="cluster"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28093"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.15-ndb-6.1.7"/>
-    </versions>
-
-    <message>
-
-      <para>
-        The cluster waited 30 seconds instead of 30 milliseconds before
-        reading table statistics.
-      </para>
-
-    </message>
-
-  </logentry>
-
   <logentry entrytype="feature">
 
     <tags>

@@ -122091,8 +121554,9 @@
     </bugs>
 
     <versions>
-      <version ver="5.0.45"/>
       <version ver="5.0.44"/>
+      <version ver="5.0.45"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 

@@ -122961,28 +122425,6 @@
   <logentry entrytype="bug">
 
     <bugs>
-      <fixes bugid="28899"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.19-ndb-6.2.3"/>
-      <version ver="5.1.15-ndb-6.1.11"/>
-    </versions>
-
-    <message>
-
-      <para>
-        It was not not possible to set a separate watchdog timeout at
-        startup.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <bugs>
       <fixes bugid="15521"/>
     </bugs>
 

@@ -123088,7 +122530,9 @@
 
     <tags>
       <highlight type="diskdata"/>
+      <manual type="ndbrequire"/>
       <manual type="cluster"/>
+      <manual type="PGMAN"/>
     </tags>
 
     <bugs>

@@ -123096,6 +122540,8 @@
     </bugs>
 
     <versions>
+      <version ver="5.1.15-ndb-6.1.10"/>
+      <version ver="5.1.19-ndb-6.2.3"/>
       <version ver="5.1.20"/>
     </versions>
 

@@ -123104,7 +122550,8 @@
       <para>
         When loading data into a cluster following a version upgrade,
         the data nodes could forcibly shut down due to page and buffer
-        management failures.
+        management failures (that is, <literal>ndbrequire</literal>
+        failures in <literal>PGMAN</literal>).
       </para>
 
     </message>

@@ -127148,31 +126595,6 @@
 
   </logentry>
 
-  <logentry entrytype="bug">
-
-    <tags>
-      <manual type="UPDATE IGNORE"/>
-    </tags>
-
-    <bugs>
-      <fixes bugid="28719"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.19-ndb-6.2.3"/>
-    </versions>
-
-    <message>
-
-      <para>
-        <literal>UPDATE IGNORE</literal> statements involving the
-        primary keys of multiple tables could result in data corruption.
-      </para>
-
-    </message>
-
-  </logentry>
-
   <logentry entrytype="feature">
 
     <bugs>

@@ -127577,6 +126999,8 @@
 
     <tags>
       <manual type="FILE"/>
+      <manual type="INFORMATION_SCHEMA"/>
+      <manual type="Access denied"/>
     </tags>
 
     <bugs>

@@ -127586,15 +127010,16 @@
     <versions>
       <version ver="5.0.42"/>
       <version ver="5.0.45"/>
+      <version ver="5.1.18"/>
     </versions>
 
     <message>
 
       <para>
         <literal>SELECT * INTO OUTFILE ... FROM
-        INFORMATION_SCHEMA.schemata</literal> failed with an
-        <literal>Access denied</literal> error, even for a user who has
-        the <literal>FILE</literal> privilege.
+        INFORMATION_SCHEMA.SCHEMATA</literal> failed with an
+        <errortext>Access denied</errortext> error, even for a user who
+        had the <literal>FILE</literal> privilege.
       </para>
 
     </message>

@@ -135449,34 +134874,7 @@
 
   <logentry entrytype="bug">
 
-    <tags>
-      <manual type="FILE"/>
-    </tags>
-
     <bugs>
-      <fixes bugid="28181"/>
-    </bugs>
-
-    <versions>
-      <version ver="5.1.18"/>
-    </versions>
-
-    <message>
-
-      <para>
-        <literal>SELECT * INTO OUTFILE ... FROM
-        INFORMATION_SCHEMA.SCHEMATA</literal> failed with an
-        <literal>Access denied</literal> error, even for a user who has
-        the <literal>FILE</literal> privilege.
-      </para>
-
-    </message>
-
-  </logentry>
-
-  <logentry entrytype="bug">
-
-    <bugs>
       <fixes bugid="28641"/>
     </bugs>
 


Thread
svn commit - mysqldoc@docsrva: r8793 - trunk/dynamic-docs/changelogjon20 Nov