Author: jstephens
Date: 2007-11-19 17:51:46 +0100 (Mon, 19 Nov 2007)
New Revision: 8789
Log:
Consolidated some more 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-19 16:42:52 UTC (rev 8788)
+++ trunk/dynamic-docs/changelog/dupes.txt 2007-11-19 16:51:46 UTC (rev 8789)
Changed blocks: 2, Lines Added: 27, Lines Deleted: 26; 738 bytes
@@ -296,32 +296,33 @@
27203x
27205x
27210x
-27254X
-27283X
-27286
-27291
-27362
-27437
-27466
-27515
-27529
-27543
-27560
-27581
-27592
-27640
-27651
-27683
-27728
-27748
+27254x
+27283x
+27286x
+27291x
+27362x
+27437x
+27466x
+27513x
+27515x
+27529x
+27543x
+27560x
+27581x
+27592x
+27640x
+27651x
+27683x
+27728x
+27748x
27756x
-27757
-27878
-27937
-27942
-27998
-28023
-28073
+27757x
+27878x
+27937x
+27942x
+27998x
+28023x
+28073x
28093
28161
28181
@@ -369,7 +370,7 @@
29570
29804
29856
-30024
+30024x
30084
30624
30681
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-19 16:42:52 UTC (rev 8788)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-19 16:51:46 UTC (rev 8789)
Changed blocks: 54, Lines Added: 73, Lines Deleted: 656; 22146 bytes
@@ -8044,34 +8044,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="cluster"/>
- <highlight type="cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="27466"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.6"/>
- </versions>
-
- <message>
-
- <para>
- A data node failing while another data node was restarting could
- leave the cluster in an inconsistent state. In certain rare
- cases, this could lead to a race condition and the eventual
- forced shutdown of the cluster.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="EXISTS"/>
</tags>
@@ -8563,6 +8535,7 @@
<versions>
<version ver="5.1.15-ndb-6.1.8"/>
+ <version ver="5.1.19"/>
</versions>
<message>
@@ -12976,6 +12949,7 @@
</bugs>
<versions>
+ <version ver="5.1.15-ndb-6.1.6"/>
<version ver="5.1.18"/>
</versions>
@@ -13696,33 +13670,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="ORDER BY RAND"/>
- <manual type="UNION"/>
- </tags>
-
- <bugs>
- <fixes bugid="27937"/>
- </bugs>
-
- <versions>
- <version ver="4.1.23"/>
- </versions>
-
- <message>
-
- <para>
- The second execution of a prepared statement from a
- <literal>UNION</literal> query with <literal>ORDER BY
- RAND()</literal> caused the server to crash.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="transactions"/>
</tags>
@@ -19237,31 +19184,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="DATETIME"/>
- </tags>
-
- <bugs>
- <fixes bugid="27592"/>
- </bugs>
-
- <versions>
- <version ver="5.0.46"/>
- </versions>
-
- <message>
-
- <para>
- A stack overrun could when storing <literal>DATETIME</literal>
- values using repeated prepared statements.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="UNSIGNED"/>
<manual type="CAST"/>
<manual type="BIGINT"/>
@@ -19706,31 +19628,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <manual type="IN"/>
- </tags>
-
- <bugs>
- <fixes bugid="27362"/>
- </bugs>
-
- <versions>
- <version ver="5.0.41"/>
- </versions>
-
- <message>
-
- <para>
- Evaluation of an <literal>IN()</literal> predicate containing a
- decimal-valued argument caused a server crash.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -20144,6 +20041,7 @@
</bugs>
<versions>
+ <version ver="5.1.22-ndb-6.2.6"/>
<version ver="5.1.23"/>
</versions>
@@ -24374,31 +24272,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <highlight type="cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="27942"/>
- </bugs>
-
- <versions>
- <version ver="5.1.19"/>
- </versions>
-
- <message>
-
- <para>
- (Disk Data): Extremely large inserts into Disk Data tables could
- lead to data node failure in some circumstances.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -27309,7 +27182,8 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
+ <highlight type="replication"/>
+ <manual type="cluster"/>
</tags>
<bugs>
@@ -27317,9 +27191,11 @@
</bugs>
<versions>
+ <version ver="4.1.23"/>
<version ver="5.0.40"/>
<version ver="5.0.41"/>
- <version ver="4.1.23"/>
+ <version ver="5.1.15-ndb-6.1.7"/>
+ <version ver="5.1.18"/>
</versions>
<message>
@@ -32176,33 +32052,6 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
- <manual type="transactions"/>
- </tags>
-
- <bugs>
- <fixes bugid="27757"/>
- </bugs>
-
- <versions>
- <version ver="5.1.18"/>
- </versions>
-
- <message>
-
- <para>
- (Disk Data): Changes to a Disk Data table made as part of a
- transaction could not be seen by the client performing the
- changes until the transaction had been committed.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="mysqldump"/>
<manual type="complete-insert"/>
</tags>
@@ -33382,6 +33231,7 @@
</bugs>
<versions>
+ <version ver="5.1.15-ndb-6.1.7"/>
<version ver="5.1.18"/>
</versions>
@@ -36121,27 +35971,6 @@
<logentry entrytype="bug">
- <bugs>
- <fixes bugid="28023"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.7"/>
- </versions>
-
- <message>
-
- <para>
- Under some circumstances, a node restart could fail to update
- the Global Checkpoint Index (GCI).
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
<tags>
<manual type="DELETE"/>
</tags>
@@ -37436,6 +37265,7 @@
<versions>
<version ver="5.0.40"/>
+ <version ver="5.0.41"/>
<version ver="5.1.18"/>
</versions>
@@ -37531,32 +37361,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <manual type="LockPagesInMainMemory"/>
- </tags>
-
- <bugs>
- <fixes bugid="27291"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.6"/>
- </versions>
-
- <message>
-
- <para>
- It was not possible to set
- <literal>LockPagesInMainMemory</literal> equal to
- <literal>0</literal>.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -38581,6 +38385,8 @@
<tags>
<highlight type="clusterreplication"/>
+ <manual type="cluster"/>
+ <manual type="replication"/>
</tags>
<bugs>
@@ -38589,6 +38395,7 @@
<versions>
<version ver="5.1.15-ndb-6.1.7"/>
+ <version ver="5.1.18"/>
</versions>
<message>
@@ -39498,33 +39305,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <highlight type="cluster"/>
- <manual type="cluster"/>
- <manual type="START BACKUP WAIT COMPLETED"/>
- </tags>
-
- <bugs>
- <fixes bugid="27640"/>
- </bugs>
-
- <versions>
- <version ver="5.1.19-ndb-6.2.3"/>
- </versions>
-
- <message>
-
- <para>
- The management client's response to <literal>START BACKUP WAIT
- COMPLETED</literal> did not include the backup ID.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -43533,6 +43313,7 @@
<manual type="ORDER BY RAND"/>
<manual type="UNION"/>
<manual type="stored procedure"/>
+ <manual type="prepared statements"/>
</tags>
<bugs>
@@ -43540,11 +43321,22 @@
</bugs>
<versions>
- <version ver="5.0.45"/>
+ <version ver="4.1.23"/>
<version ver="5.0.44"/>
+ <version ver="5.0.45"/>
<version ver="5.1.19"/>
</versions>
+ <message ver="4.1.23">
+
+ <para>
+ The second execution of a prepared statement from a
+ <literal>UNION</literal> query with <literal>ORDER BY
+ RAND()</literal> caused the server to crash.
+ </para>
+
+ </message>
+
<message>
<para>
@@ -44723,6 +44515,7 @@
<tags>
<manual type="DATETIME"/>
+ <manual type="prepared statements"/>
</tags>
<bugs>
@@ -44730,6 +44523,7 @@
</bugs>
<versions>
+ <version ver="5.0.46"/>
<version ver="5.1.20"/>
</versions>
@@ -45164,6 +44958,8 @@
<tags>
<highlight type="clusterreplication"/>
<manual type="replication"/>
+ <manual type="cluster"/>
+ <manual type="max-relay-log-size"/>
</tags>
<bugs>
@@ -45171,8 +44967,8 @@
</bugs>
<versions>
- <version ver="5.1.18-ndb-6.2.1"/>
<version ver="5.1.15-ndb-6.1.6"/>
+ <version ver="5.1.18"/>
</versions>
<message>
@@ -53338,34 +53134,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <highlight type="cluster"/>
- <manual type="replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="27529"/>
- </bugs>
-
- <versions>
- <version ver="5.1.18"/>
- </versions>
-
- <message>
-
- <para>
- (Replication): Trying to replicate a large number of frequent
- updates with a relatively small relay log
- (<literal>max-relay-log-size</literal> set to 1M or less) could
- cause the slave to crash.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -55019,32 +54787,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="mysqld"/>
- </tags>
-
- <bugs>
- <fixes bugid="27560"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.7"/>
- <version ver="5.1.18-ndb-6.2.1"/>
- </versions>
-
- <message>
-
- <para>
- Memory usage of a <command>mysqld</command> process grew even
- while idle.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="SSL"/>
<manual type="mysqldump"/>
</tags>
@@ -56946,35 +56688,6 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
- <manual type="ndbd"/>
- <manual type="transactions"/>
- </tags>
-
- <bugs>
- <fixes bugid="28073"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.7"/>
- </versions>
-
- <message>
-
- <para>
- Under certain rare circumstances, <command>ndbd</command> could
- get caught in an infinite loop when one transaction took a read
- lock and then a second transaction attempted to obtain a write
- lock on the same tuple in the lock queue.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="SQL_CALC_FOUND_ROWS"/>
<manual type="ROLLUP"/>
<manual type="LIMIT"/>
@@ -61264,33 +60977,6 @@
<logentry entrytype="bug">
<tags>
- <highlight type="securityfix"/>
- <manual type="RENAME TABLE"/>
- <manual type="DROP"/>
- </tags>
-
- <bugs>
- <fixes bugid="27515"/>
- </bugs>
-
- <versions>
- <version ver="5.0.45"/>
- </versions>
-
- <message>
-
- <para>
- The requirement of the <literal>DROP</literal> privilege for
- <literal>RENAME TABLE</literal> was not being enforced.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<highlight type="cluster"/>
<manual type="cluster"/>
</tags>
@@ -63308,6 +62994,7 @@
</bugs>
<versions>
+ <version ver="5.1.15-ndb-6.1.7"/>
<version ver="5.1.18"/>
</versions>
@@ -75511,32 +75198,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <highlight type="cluster"/>
- <manual type="replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="27748"/>
- </bugs>
-
- <versions>
- <version ver="5.1.18"/>
- </versions>
-
- <message>
-
- <para>
- Some queries that updated multiple tables were not backed up or
- replicated correctly.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -76425,36 +76086,6 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
- <manual type="BLOB"/>
- <manual type="cluster"/>
- <manual type="DATETIME"/>
- </tags>
-
- <bugs>
- <fixes bugid="27543"/>
- <fixes bugid="30024"/>
- </bugs>
-
- <versions>
- <version ver="5.1.22-ndb-6.2.6"/>
- </versions>
-
- <message>
-
- <para>
- Restoring a backup made on a cluster host using one endian to a
- machine using the other endian failed for
- <literal>BLOB</literal> and <literal>DATETIME</literal> columns.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="lower_case_table_names"/>
</tags>
@@ -77180,31 +76811,6 @@
<logentry entrytype="bug">
<tags>
- <manual type="replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="27748"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.7"/>
- </versions>
-
- <message>
-
- <para>
- Some queries that updated multiple tables were not backed up or
- replicated correctly.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<highlight type="diskdata"/>
<manual type="cluster"/>
</tags>
@@ -80901,35 +80507,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <highlight type="cluster"/>
- <manual type="help"/>
- <manual type="ndb_restore"/>
- <manual type="print"/>
- </tags>
-
- <bugs>
- <fixes bugid="27683"/>
- </bugs>
-
- <versions>
- <version ver="5.1.22-ndb-6.2.6"/>
- </versions>
-
- <message>
-
- <para>
- The description of the <option>--print</option> option in the
- output from <command>ndb_restore
- <option>--help</option></command> was incorrect.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -81491,15 +81068,17 @@
<versions>
<version ver="5.0.40"/>
<version ver="5.0.41"/>
+ <version ver="5.1.15-ndb-6.1.7"/>
<version ver="5.1.18"/>
</versions>
<message>
<para>
- Under certain rare circumstances, <literal>DROP TABLE</literal>
- or <literal>TRUNCATE</literal> of an <literal>NDB</literal>
- table could cause a node failure or forced cluster shutdown.
+ Under certain rare circumstances performing a <literal>DROP
+ TABLE</literal> or <literal>TRUNCATE</literal> on an
+ <literal>NDB</literal> table could cause a node failure or
+ forced cluster shutdown.
</para>
</message>
@@ -84966,32 +84545,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <highlight type="cluster"/>
- <manual type="replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="27651"/>
- </bugs>
-
- <versions>
- <version ver="5.1.18"/>
- </versions>
-
- <message>
-
- <para>
- (Replication): Under very high loads, checkpoints could be read
- or written with checkpoint indexes out of order.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -85331,6 +84884,7 @@
<versions>
<version ver="5.0.40"/>
<version ver="5.0.41"/>
+ <version ver="5.1.15-ndb-6.1.6"/>
<version ver="5.1.17"/>
</versions>
@@ -93343,34 +92897,6 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <highlight type="cluster"/>
- <manual type="cluster"/>
- <manual type="mysqldump"/>
- </tags>
-
- <bugs>
- <fixes bugid="27437"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.8"/>
- </versions>
-
- <message>
-
- <para>
- Repeated insertion of data generated by
- <command>mysqldump</command> into <literal>NDB</literal> tables
- could eventually lead to failure of the cluster.
- </para>
-
- </message>
-
- </logentry>
-
<logentry entrytype="feature">
<tags>
@@ -101734,20 +101260,34 @@
</bugs>
<versions>
+ <version ver="4.1.23"/>
+ <version ver="5.0.44"/>
+ <version ver="5.0.45"/>
<version ver="5.1.19"/>
</versions>
<message>
<para>
- <literal>INSERT DELAYED</literal> statements for
- <literal>BLACKHOLE</literal> tables caused a server crash. The
- <literal>BLACKHOLE</literal> storage engine now supports
- <literal>INSERT DELAYED</literal>.
+ <literal>INSERT DELAYED</literal> statements on
+ <literal>BLACKHOLE</literal> tables are now rejected, due to the
+ fact that the <literal>BLACKHOLE</literal> storage engine does
+ not support them.
</para>
</message>
+ <message ver="5.1.19">
+
+ <para>
+ The <literal>BLACKHOLE</literal> storage engine now supports
+ <literal>INSERT DELAYED</literal>. Previously, <literal>INSERT
+ DELAYED</literal> statements for <literal>BLACKHOLE</literal>
+ tables were not supported, and caused the server to crash.
+ </para>
+
+ </message>
+
</logentry>
<logentry entrytype="bug">
@@ -102037,6 +101577,7 @@
<versions>
<version ver="5.0.40"/>
<version ver="5.0.41"/>
+ <version ver="5.1.15-ndb-6.1.6"/>
<version ver="5.1.17"/>
</versions>
@@ -102197,35 +101738,6 @@
<logentry entrytype="bug">
<tags>
- <highlight type="cluster"/>
- <manual type="cluster"/>
- <manual type="TRUNCATE"/>
- <manual type="DROP TABLE"/>
- </tags>
-
- <bugs>
- <fixes bugid="27581"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.7"/>
- </versions>
-
- <message>
-
- <para>
- Under certain rare circumstances, <literal>DROP TABLE</literal>
- or <literal>TRUNCATE</literal> of an <literal>NDB</literal>
- table could cause a node failure or forced cluster shutdown.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="ledir"/>
<manual type="mysqld_safe"/>
</tags>
@@ -107396,14 +106908,15 @@
<versions>
<version ver="5.0.50"/>
+ <version ver="5.1.22-ndb-6.2.6"/>
<version ver="5.1.23"/>
</versions>
<message>
<para>
- The description of the <option>--print</option> option in the
- output from <command>ndb_restore <option>--help</option>
+ The description of the <option>--print</option> option provided
+ in the output from <command>ndb_restore <option>--help</option>
</command> was incorrect.
</para>
@@ -108819,28 +108332,6 @@
<logentry entrytype="bug">
- <bugs>
- <fixes bugid="27286"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.6"/>
- </versions>
-
- <message>
-
- <para>
- A race condition could sometimes occur if the node acting as
- master failed while node IDs were still being allocated during
- startup.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
<tags>
<manual type="LIKE"/>
<manual type="character sets"/>
@@ -112701,6 +112192,7 @@
<versions>
<version ver="5.1.15-ndb-6.1.7"/>
+ <version ver="5.1.18"/>
</versions>
<message>
@@ -115295,31 +114787,6 @@
<logentry entrytype="bug">
<tags>
- <highlight type="securityfix"/>
- </tags>
-
- <bugs>
- <fixes bugid="27878"/>
- </bugs>
-
- <versions>
- <version ver="5.0.45"/>
- </versions>
-
- <message>
-
- <para>
- Use of a view could allow a user to gain update privileges for
- tables in other databases.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="BLOB"/>
<manual type="myisampack"/>
</tags>
@@ -119839,6 +119306,7 @@
<versions>
<version ver="5.0.40"/>
<version ver="5.0.41"/>
+ <version ver="5.1.15-ndb-6.1.7"/>
<version ver="5.1.18"/>
</versions>
@@ -121592,8 +121060,9 @@
</bugs>
<versions>
- <version ver="5.0.42"/>
<version ver="4.1.23"/>
+ <version ver="5.0.42"/>
+ <version ver="5.0.45"/>
<version ver="5.1.18"/>
</versions>
@@ -121601,7 +121070,7 @@
<para>
The requirement of the <literal>DROP</literal> privilege for
- <literal>RENAME TABLE</literal> was not being enforced.
+ <literal>RENAME TABLE</literal> was not enforced.
</para>
</message>
@@ -121993,6 +121462,7 @@
</bugs>
<versions>
+ <version ver="5.1.15-ndb-6.1.7"/>
<version ver="5.1.18"/>
</versions>
@@ -124036,6 +123506,7 @@
<versions>
<version ver="5.0.42"/>
<version ver="5.0.45"/>
+ <version ver="5.1.15-ndb-6.1.8"/>
<version ver="5.1.19"/>
</versions>
@@ -128838,36 +128309,7 @@
<logentry entrytype="bug">
- <tags>
- <manual type="INSERT DELAYED"/>
- <manual type="BLACKHOLE"/>
- </tags>
-
<bugs>
- <fixes bugid="27998"/>
- </bugs>
-
- <versions>
- <version ver="5.0.45"/>
- <version ver="5.0.44"/>
- <version ver="4.1.23"/>
- </versions>
-
- <message>
-
- <para>
- The <literal>BLACKHOLE</literal> storage engine does not support
- <literal>INSERT DELAYED</literal> statements, but they were not
- being rejected.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <bugs>
<fixes bugid="6387"/>
<fixes bugid="9455"/>
</bugs>
@@ -130562,14 +130004,15 @@
<versions>
<version ver="5.0.46"/>
+ <version ver="5.1.19-ndb-6.2.3"/>
<version ver="5.1.20"/>
</versions>
<message>
<para>
- The management client's response to <literal>START BACKUP WAIT
- COMPLETED</literal> did not include the backup ID.
+ The management client's response to <literal>START BACKUP
+ WAIT COMPLETED</literal> did not include the backup ID.
</para>
</message>
@@ -133201,6 +132644,7 @@
<versions>
<version ver="5.0.42"/>
+ <version ver="5.0.45"/>
<version ver="5.1.19"/>
</versions>
@@ -134354,33 +133798,6 @@
<logentry entrytype="bug">
<tags>
- <highlight type="clusterreplication"/>
- <manual type="cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="27728"/>
- </bugs>
-
- <versions>
- <version ver="5.1.15-ndb-6.1.7"/>
- </versions>
-
- <message>
-
- <para>
- It was possible for API nodes to begin interacting with the
- cluster subscription manager before they were fully connected to
- the cluster.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
<manual type="configure"/>
</tags>
@@ -134396,8 +133813,8 @@
<message>
<para>
- Fixed <command>configure</command> to properly recognize whether
- NPTL is available on Linux.
+ <command>configure</command> did not properly recognize whether
+ NPTL was available on Linux.
</para>
</message>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8789 - trunk/dynamic-docs/changelog | jon | 19 Nov |
