| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | November 20 2007 6:06pm |
| Subject: | svn commit - mysqldoc@docsrva: r8800 - trunk/dynamic-docs/changelog | ||
| View as plain text | |||
Author: jstephens Date: 2007-11-20 18:06:16 +0100 (Tue, 20 Nov 2007) New Revision: 8800 Log: Remaining duplicate changelog bugfix entries Minor fixes to duplicate detection script Modified: trunk/dynamic-docs/changelog/dupes.txt trunk/dynamic-docs/changelog/get-dupes trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/dupes.txt =================================================================== --- trunk/dynamic-docs/changelog/dupes.txt 2007-11-20 16:30:23 UTC (rev 8799) +++ trunk/dynamic-docs/changelog/dupes.txt 2007-11-20 17:06:16 UTC (rev 8800) Changed blocks: 2, Lines Added: 27, Lines Deleted: 25; 733 bytes @@ -249,6 +249,7 @@ 25296x 25422x 25530x +25564x 25578x 25621x 25686x @@ -348,32 +349,33 @@ 28899x 28949x 28984x -29044 -29057 -29063 -29067 -29074 -29102 -29103 -29118 +29044x +29057x +29063x +29067x +29074x +29102x +29103x +29118x 29129x -29167 -29176 -29185 -29228 -29229 -29331 -29354 -29364 +29167x +29176x +29185x +29228x +29229x +29331x +29354x +29364x 29474x -29501 -29570 -29804 -29856 +29501x +29570x +29804x +29856x 30024x -30084 -30624 -30681 -30764 -30914 +30084x +30088x +30624x +30681x +30764x +30914x Modified: trunk/dynamic-docs/changelog/get-dupes =================================================================== --- trunk/dynamic-docs/changelog/get-dupes 2007-11-20 16:30:23 UTC (rev 8799) +++ trunk/dynamic-docs/changelog/get-dupes 2007-11-20 17:06:16 UTC (rev 8800) Changed blocks: 2, Lines Added: 6, Lines Deleted: 4; 766 bytes @@ -1,9 +1,9 @@ #!/usr/bin/php -# USAGE: ./get-dupes > file.ext - <?php +# USAGE: ./get-dupes [> file.ext] + $doc = DOMdocument::load('mysqld.xml'); $bugs = array(); @@ -23,9 +23,11 @@ $dupes []= $bugid; sort($dupes); + + $count = count($dupes); - echo "\nDuplicate Bugs: " . count($dupes) . "\n\nDuplicate Bug IDs:\n"; + echo "\nDuplicate Bugs: $count\n\nDuplicate Bug IDs:"; - echo implode("\n", $dupes); +echo ($count > 0 ? "\n\n" . implode("\n", $dupes) : " [none]") . "\n\n"; ?> Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-20 16:30:23 UTC (rev 8799) +++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-20 17:06:16 UTC (rev 8800) Changed blocks: 83, Lines Added: 164, Lines Deleted: 1118; 39251 bytes @@ -1890,6 +1890,7 @@ <tags> <manual type="DROP TABLE"/> + <manual type="CREATE TABLE ... SELECT ..."/> </tags> <bugs> @@ -1898,13 +1899,15 @@ <versions> <version ver="5.2.1"/> + <version ver="6.0.0"/> </versions> <message> <para> - MySQL crashes during <literal>DROP TABLE</literal> after - <literal>CREATE TABLE ... SELECT *</literal>. + A <literal>DROP TABLE</literal> statement on a table created + using <literal>CREATE TABLE ... SELECT ...</literal> crashed the + server. </para> </message> @@ -2944,32 +2947,7 @@ <logentry entrytype="bug"> - <tags> - <manual type="DROP TABLE"/> - </tags> - <bugs> - <fixes bugid="25564"/> - </bugs> - - <versions> - <version ver="6.0.0"/> - </versions> - - <message> - - <para> - Executing <literal>DROP TABLE</literal> on a table that has been - created using <literal>CREATE TABLE ... SELECT</literal>. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <bugs> <fixes bugid="27993"/> </bugs> @@ -6136,9 +6114,12 @@ <bugs> <fixes bugid="29102"/> + <seealsobug bugid="31482"/> </bugs> <versions> + <version ver="5.0.50"/> + <version ver="5.1.22-ndb-6.2.5"/> <version ver="5.1.23"/> </versions> @@ -6146,7 +6127,7 @@ <para> Reads on <literal>BLOB</literal> columns were not locked when - they needed to be, in order to guarantee consistency. + they needed to be to guarantee consistency. </para> </message> @@ -7550,14 +7531,15 @@ </bugs> <versions> + <version ver="4.1.16"/> <version ver="5.0.16"/> </versions> <message> <para> - MySQL 5.0 now supports character set conversion for seven - additional <literal>cp950</literal> characters into the + MySQL ¤t-series; now supports character set conversion for + seven additional <literal>cp950</literal> characters into the <literal>big5</literal> character set: <literal>0xF9D6</literal>, <literal>0xF9D7</literal>, <literal>0xF9D8</literal>, <literal>0xF9D9</literal>, @@ -10859,10 +10841,12 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> + <highlight type="clusterreplication"/> + <manual type="cluster"/> <manual type="replication"/> <manual type="DELETE"/> <manual type="INSERT"/> + <manual type="multi-master"/> </tags> <bugs> @@ -10870,14 +10854,15 @@ </bugs> <versions> + <version ver="5.1.15-ndb-6.1.20"/> <version ver="5.1.23"/> </versions> <message> <para> - (Replication): Incorrect handling of <literal>INSERT</literal> - plus <literal>DELETE</literal> operations with regard to local + Incorrect handling of <literal>INSERT</literal> plus + <literal>DELETE</literal> operations with regard to local checkpoints caused data node failures in multi-master replication setups. </para> @@ -16912,6 +16897,7 @@ <tags> <manual type="mysql_install_db"/> + <manual type="i5"/> </tags> <bugs> @@ -16919,20 +16905,55 @@ </bugs> <versions> + <version ver="5.0.42"/> + <version ver="5.0.44"/> <version ver="5.0.45"/> + <version ver="5.0.46"/> </versions> - <message> + <message ver="5.0.42"> <para> - On the IBM i5 platform, the installation script in *SAVF - binaries unconditionally executed the + On the IBM i5 platform, the installation script in the + <filename>.savf</filename> binaries unconditionally executed the <command>mysql_install_db</command> script. This problem was + fixed in a repackaged distribution numbered 5.0.42b. + </para> + + </message> + + <message ver="5.0.44"> + + <para> + On the IBM i5 platform, the installation script in the + <filename>.savf</filename> binaries unconditionally executed the + <command>mysql_install_db</command> script. This problem was + fixed in a repackaged distribution numbered 5.0.44b. + </para> + + </message> + + <message ver="5.0.45"> + + <para> + On the IBM i5 platform, the installation script in the + <filename>.savf</filename> binaries unconditionally executed the + <command>mysql_install_db</command> script. This problem was fixed in a repackaged distribution numbered 5.0.45b. </para> </message> + <message ver="5.0.46"> + + <para> + On the IBM i5 platform, the installation script in the + <filename>.savf</filename> binaries unconditionally executed the + <command>mysql_install_db</command> script. + </para> + + </message> + </logentry> <logentry entrytype="bug"> @@ -17199,6 +17220,7 @@ </bugs> <versions> + <version ver="5.1.15-ndb-6.1.18"/> <version ver="5.1.21"/> </versions> @@ -19138,35 +19160,6 @@ <logentry entrytype="bug"> <tags> - <manual type="UNSIGNED"/> - <manual type="CAST"/> - <manual type="BIGINT"/> - </tags> - - <bugs> - <fixes bugid="8663"/> - </bugs> - - <versions> - <version ver="4.1.22"/> - </versions> - - <message> - - <para> - The result for <literal>CAST()</literal> when casting a value to - <literal>UNSIGNED</literal> was limited to the maximum signed - <literal>BIGINT</literal> value (9223372036854775808), not the - maximum unsigned value (18446744073709551615). - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <highlight type="cluster"/> <manual type="transactions"/> <manual type="cluster"/> @@ -25762,7 +25755,7 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> + <highlight type="diskdata"/> </tags> <bugs> @@ -25770,15 +25763,17 @@ </bugs> <versions> - <version ver="5.1.20"/> + <version ver="5.1.15-ndb-6.1.16"/> + <version ver="5.1.19-ndb-6.2.3"/> + <version ver="5.1.21"/> </versions> <message> <para> - (Disk Data): When dropping a page, the stack's bottom entry - could sometime be left <quote>cold</quote> rather than - <quote>hot</quote>, violating the rules for stack pruning. + When dropping a page, the stack's bottom entry could sometime be + left <quote>cold</quote> rather than <quote>hot</quote>, + violating the rules for stack pruning. </para> </message> @@ -29798,6 +29793,7 @@ <logentry entrytype="bug"> <tags> + <highlight type="cluster"/> <manual type="MaxAllocate"/> </tags> @@ -29806,8 +29802,9 @@ </bugs> <versions> - <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.15-ndb-6.1.12"/> + <version ver="5.1.19-ndb-6.2.3"/> + <version ver="5.1.20"/> </versions> <message> @@ -31827,32 +31824,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> - </tags> - - <bugs> - <introducedby bugid="29354"/> - </bugs> - - <versions> - <version ver="5.1.21"/> - <version ver="5.0.46"/> - </versions> - - <message> - - <para> - A problem with the fix for Bug #29354 caused an assertion when - two local checkpoints were run during node recovery. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="mysqldump"/> </tags> @@ -32017,35 +31988,6 @@ <logentry entrytype="bug"> <tags> - <manual type="WHERE"/> - <manual type="cluster"/> - <manual type="mysqld"/> - </tags> - - <bugs> - <fixes bugid="29185"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - </versions> - - <message> - - <para> - A query having a large <literal>IN(...)</literal> or - <literal>NOT IN(...)</literal> list in the - <literal>WHERE</literal> condition on an <literal>NDB</literal> - table could cause <command>mysqld</command> to crash. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type=".idb"/> <manual type="InnoDB"/> </tags> @@ -35173,6 +35115,10 @@ <logentry entrytype="bug"> <tags> + <manual type="stored routine"/> + <manual type="prepared statement"/> + <manual type="CREATE DATABASE"/> + <manual type="CREATE TABLE"/> <manual type="ALTER TABLE"/> <manual type="AUTO_INCREMENT"/> </tags> @@ -35192,6 +35138,28 @@ <version ver="5.1.20"/> </versions> + <message ver="4.1.23"> + + <para> + The internal functions for table preparation, creation, and + alteration were not re-execution friendly, causing problems in + code that: repeatedly altered a table; repeatedly created and + dropped a table; opened and closed a cursor on a table, altered + the table, and then reopened the cursor; used <literal>ALTER + TABLE</literal> to change a table's current + <literal>AUTO_INCREMENT</literal> value; created indexes on + <literal>utf8</literal> columns. + </para> + + <para> + Re-execution of <literal>CREATE DATABASE</literal>, + <literal>CREATE TABLE</literal>, and <literal>ALTER + TABLE</literal> statements as prepared statements also caused + incorrect results or crashes. + </para> + + </message> + <message> <para> @@ -35205,6 +35173,13 @@ <literal>utf8</literal> columns. </para> + <para> + Re-execution of <literal>CREATE DATABASE</literal>, + <literal>CREATE TABLE</literal>, and <literal>ALTER + TABLE</literal> statements in stored routines or as prepared + statements also caused incorrect results or crashes. + </para> + </message> </logentry> @@ -35513,6 +35488,9 @@ </bugs> <versions> + <version ver="5.0.46"/> + <version ver="5.1.15-ndb-6.1.17"/> + <version ver="5.1.19-ndb-6.2.4"/> <version ver="5.1.21"/> </versions> @@ -37970,29 +37948,6 @@ <logentry entrytype="bug"> - <bugs> - <fixes bugid="29364"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.4"/> - <version ver="5.1.15-ndb-6.1.18"/> - </versions> - - <message> - - <para> - When restarting a data node, queries could hang during that - node's start phase 5, and only continue once the node entered - phase 6. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - <tags> <manual type="dlopen"/> <manual type="HP-UX"/> @@ -40913,6 +40868,7 @@ <tags> <manual type="stored procedure"/> + <manual type="prepared statement"/> </tags> <bugs> @@ -42170,33 +42126,6 @@ <logentry entrytype="bug"> <tags> - <manual type="COPY_GCI"/> - </tags> - - <bugs> - <fixes bugid="29331"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - <version ver="5.1.15-ndb-6.1.16"/> - </versions> - - <message> - - <para> - When a node failed to respond to a <literal>COPY_GCI</literal> - signal as part of a global checkpoint, the master node was - killed instead instead of the node that actually failed. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="AFTER UPDATE"/> <manual type="MyISAM"/> <manual type="AFTER INSERT"/> @@ -43985,35 +43914,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="api"/> - <manual type="mgmapi.cpp"/> - <manual type="CHECK_TIMEDOUT_RET"/> - <manual type="DBUG_CHECK_TIMEDOUT_RET"/> - </tags> - - <bugs> - <fixes bugid="30681"/> - </bugs> - - <versions> - <version ver="5.1.22-ndb-6.2.5"/> - </versions> - - <message> - - <para> - A call to <literal>CHECK_TIMEDOUT_RET()</literal> in - <filename>mgmapi.cpp</filename> should have been a call to - <literal>DBUG_CHECK_TIMEDOUT_RET()</literal>. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="CREATE"/> </tags> @@ -47202,37 +47102,6 @@ <logentry entrytype="bug"> <tags> - <manual type="stored routine"/> - <manual type="CREATE DATABASE"/> - <manual type="CREATE TABLE"/> - <manual type="ALTER TABLE"/> - </tags> - - <bugs> - <fixes bugid="22060"/> - </bugs> - - <versions> - <version ver="5.0.36"/> - <version ver="5.0.37"/> - </versions> - - <message> - - <para> - Re-execution of <literal>CREATE DATABASE</literal>, - <literal>CREATE TABLE</literal>, and <literal>ALTER - TABLE</literal> statements in stored routines or as prepared - statements caused incorrect results or crashes. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="InnoDB"/> </tags> @@ -48270,36 +48139,6 @@ <logentry entrytype="bug"> <tags> - <manual type="stored routine"/> - <manual type="CREATE DATABASE"/> - <manual type="CREATE TABLE"/> - <manual type="ALTER TABLE"/> - </tags> - - <bugs> - <fixes bugid="22060"/> - </bugs> - - <versions> - <version ver="5.1.15"/> - </versions> - - <message> - - <para> - Re-execution of <literal>CREATE DATABASE</literal>, - <literal>CREATE TABLE</literal>, and <literal>ALTER - TABLE</literal> statements in stored routines or as prepared - statements caused incorrect results. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type=".frm"/> </tags> @@ -49047,6 +48886,7 @@ <versions> <version ver="5.1.19-ndb-6.2.3"/> + <version ver="5.1.20"/> </versions> <message> @@ -50105,8 +49945,8 @@ <para> The result for <literal>CAST()</literal> when casting a value to <literal>UNSIGNED</literal> was limited to the maximum signed - <literal>BIGINT</literal> value (9223372036854775808), not the - maximum unsigned value (18446744073709551615). + <literal>BIGINT</literal> value (9223372036854775808), rather + than the maximum unsigned value (18446744073709551615). </para> </message> @@ -50728,6 +50568,7 @@ </bugs> <versions> + <version ver="5.1.22-ndb-6.2.5"/> <version ver="5.1.23"/> </versions> @@ -51636,16 +51477,18 @@ </bugs> <versions> - <version ver="5.1.21"/> <version ver="5.0.46"/> + <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> <para> When restarting a data node, queries could hang during that - node's start phase 5, and only continue once the node entered - phase 6. + node's start phase 5, and continue only after the node had + entered phase 6. </para> </message> @@ -56188,34 +56031,7 @@ <logentry entrytype="bug"> - <tags> - <highlight type="diskdata"/> - </tags> - <bugs> - <fixes bugid="29176"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - <version ver="5.1.15-ndb-6.1.14"/> - </versions> - - <message> - - <para> - When dropping a page, the stack's bottom entry could sometime be - left <quote>cold</quote> rather than <quote>hot</quote>, - violating the rules for stack pruning. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <bugs> <fixes bugid="9103"/> </bugs> @@ -56679,39 +56495,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="diskdata"/> - </tags> - - <bugs> - <fixes bugid="29176"/> - </bugs> - - <versions> - <version ver="5.1.15-ndb-6.1.16"/> - </versions> - - <message> - - <para> - When dropping a page, the stack's bottom entry could sometime be - left <quote>cold</quote> rather than <quote>hot</quote>, - violating the rules for stack pruning. - </para> - - <note> - <para> - This supersedes an earlier fix for this bug that was made in - MySQL 5.1.15-ndb-6.1.14. - </para> - </note> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -57486,13 +57269,18 @@ <logentry entrytype="bug"> + <tags> + <highlight type="cluster"/> + </tags> + <bugs> <fixes bugid="29067"/> </bugs> <versions> - <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.15-ndb-6.1.16"/> + <version ver="5.1.19-ndb-6.2.3"/> + <version ver="5.1.21"/> </versions> <message> @@ -65115,33 +64903,6 @@ </logentry> - <logentry entrytype="feature"> - - <tags> - <highlight type="cluster"/> - <manual type="MaxAllocate"/> - </tags> - - <bugs> - <fixes bugid="29044"/> - </bugs> - - <versions> - <version ver="5.1.20"/> - </versions> - - <message> - - <para> - It is now possible to set the maximum size of the allocation - unit for table memory using the <literal>MaxAllocate</literal> - configuration parameter. - </para> - - </message> - - </logentry> - <logentry entrytype="bug"> <tags> @@ -66004,13 +65765,14 @@ <versions> <version ver="5.1.22-ndb-6.3.4"/> <version ver="5.1.22-ndb-6.2.7"/> + <version ver="5.1.23"/> </versions> <message> <para> - The <command>mysqld_safe</command> script had a syntax error in - a test operation. + The <command>mysqld_safe</command> script contained a syntax + error. </para> </message> @@ -66391,33 +66153,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <manual type="mysql_install_db"/> - </tags> - - <bugs> - <fixes bugid="30084"/> - </bugs> - - <versions> - <version ver="5.0.42"/> - </versions> - - <message> - - <para> - On the IBM i5 platform, the installation script in *SAVF - binaries unconditionally executed the - <command>mysql_install_db</command> script. This problem was - fixed in a repackaged distribution numbered 5.0.42b. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -67940,6 +67675,8 @@ </bugs> <versions> + <version ver="5.1.15-ndb-6.1.16"/> + <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.21"/> </versions> @@ -68957,31 +68694,6 @@ <logentry entrytype="bug"> <tags> - <manual type="BLOB"/> - </tags> - - <bugs> - <fixes bugid="30764"/> - </bugs> - - <versions> - <version ver="5.1.22-ndb-6.2.5"/> - </versions> - - <message> - - <para> - When handling <literal>BLOB</literal> columns, the addition of - read locks to the lock queue was not handled correctly. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="BDB"/> <manual type="DELETE"/> <manual type="subqueries"/> @@ -69499,31 +69211,6 @@ <logentry entrytype="bug"> <tags> - <manual type="mysqld_safe"/> - </tags> - - <bugs> - <fixes bugid="30624"/> - </bugs> - - <versions> - <version ver="5.1.23"/> - </versions> - - <message> - - <para> - The <command>mysqld_safe</command> script had a syntax error in - a test operation. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="VAR_SAMP"/> <manual type="VAR_POP"/> <manual type="VARIANCE"/> @@ -70413,31 +70100,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="cluster"/> - </tags> - - <bugs> - <fixes bugid="29501"/> - </bugs> - - <versions> - <version ver="5.1.21"/> - </versions> - - <message> - - <para> - (Disk Data): Performing Disk Data schema operations during a - node restart could cause forced shutdowns of other data nodes. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -77281,33 +76943,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <manual type="REDO"/> - </tags> - - <bugs> - <fixes bugid="29118"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - <version ver="5.1.15-ndb-6.1.16"/> - </versions> - - <message> - - <para> - An invalid comparison made during <literal>REDO</literal> - validation that could lead to an <errortext>Error while reading - REDO log</errortext> condition. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -79097,38 +78732,6 @@ </logentry> - <logentry entrytype="feature"> - - <tags> - <manual type="character sets"/> - </tags> - - <bugs> - <fixes bugid="12476"/> - </bugs> - - <versions> - <version ver="4.1.16"/> - </versions> - - <message> - - <para> - MySQL 4.1 now supports character set conversion for seven - additional <literal>cp950</literal> characters into the - <literal>big5</literal> character set: - <literal>0xF9D6</literal>, <literal>0xF9D7</literal>, - <literal>0xF9D8</literal>, <literal>0xF9D9</literal>, - <literal>0xF9DA</literal>, <literal>0xF9DB</literal>, and - <literal>0xF9DC</literal>. Note that if you move data containing - these additional characters to an older MySQL installation which - does not support them, you may encounter errors. - </para> - - </message> - - </logentry> - <logentry entrytype="bug"> <tags> @@ -79519,32 +79122,6 @@ <logentry entrytype="bug"> <tags> - <manual type="MyISAM"/> - <manual type="myisam-recover"/> - </tags> - - <bugs> - <fixes bugid="30088"/> - </bugs> - - <versions> - <version ver="5.0.48"/> - </versions> - - <message> - - <para> - <option>--myisam-recover=""</option> (empty option - value) did not disable <literal>MyISAM</literal> recovery. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="Windows"/> </tags> @@ -80609,32 +80186,6 @@ <logentry entrytype="feature"> <tags> - <highlight type="cluster"/> - <manual type="ndb_error_reporter"/> - </tags> - - <bugs> - <fixes bugid="29074"/> - </bugs> - - <versions> - <version ver="5.1.20"/> - </versions> - - <message> - - <para> - <command>ndb_error_reporter</command> now preserves timestamps - on files. - </para> - - </message> - - </logentry> - - <logentry entrytype="feature"> - - <tags> <manual type="BLOB"/> <manual type="collation"/> <manual type="VARSTRING"/> @@ -82272,31 +81823,6 @@ <logentry entrytype="bug"> <tags> - <manual type="BLOB"/> - </tags> - - <bugs> - <fixes bugid="29102"/> - </bugs> - - <versions> - <version ver="5.1.22-ndb-6.2.5"/> - </versions> - - <message> - - <para> - Reads on <literal>BLOB</literal> columns were not locked when - they needed to be, in order to guarantee consistency. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="SHOW CREATE TABLE"/> <manual type="InnoDB"/> </tags> @@ -83387,6 +82913,7 @@ </bugs> <versions> + <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.20"/> </versions> @@ -84288,7 +83815,7 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> + <highlight type="clusterapi"/> <manual type="cluster"/> <manual type="mgmapi.cpp"/> <manual type="CHECK_TIMEDOUT_RET"/> @@ -84300,6 +83827,7 @@ </bugs> <versions> + <version ver="5.1.22-ndb-6.2.5"/> <version ver="5.1.23"/> </versions> @@ -86059,6 +85587,8 @@ </bugs> <versions> + <version ver="5.1.15-ndb-6.1.15"/> + <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.20"/> </versions> @@ -92113,35 +91643,6 @@ <logentry entrytype="bug"> <tags> - <manual type="CREATE DATABASE"/> - <manual type="CREATE TABLE"/> - <manual type="ALTER TABLE"/> - </tags> - - <bugs> - <fixes bugid="22060"/> - </bugs> - - <versions> - <version ver="4.1.23"/> - </versions> - - <message> - - <para> - Re-execution of <literal>CREATE DATABASE</literal>, - <literal>CREATE TABLE</literal>, and <literal>ALTER - TABLE</literal> statements as prepared statements caused - incorrect results or crashes. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="SSL"/> <manual type="libmysqlclient"/> <manual type="icc"/> @@ -94888,32 +94389,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="diskdata"/> - </tags> - - <bugs> - <fixes bugid="29176"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - </versions> - - <message> - - <para> - When dropping a page, the stack's bottom entry could sometime be - left <quote>cold</quote> rather than <quote>hot</quote>, - violating the rules for stack pruning. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="mysql_config"/> <manual type="zlib"/> </tags> @@ -95324,33 +94799,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="replication"/> - <manual type="replication"/> - <manual type="row-based logging"/> - </tags> - - <bugs> - <fixes bugid="29570"/> - </bugs> - - <versions> - <version ver="5.1.15-ndb-6.1.18"/> - </versions> - - <message> - - <para> - Storage engine error conditions in row-based replication were - not correctly reported to the user. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="Windows"/> <manual type="SLEEP"/> </tags> @@ -96241,6 +95689,7 @@ <versions> <version ver="4.1.21"/> <version ver="5.0.23"/> + <version ver="5.1.11"/> </versions> <message> @@ -96253,6 +95702,22 @@ </message> + <message ver="5.1.11"> + + <para> + <literal>TRUNCATE</literal> failed on tables having + <literal>BLOB</literal> or <literal>TEXT</literal> columns with + the error <errortext>Lock wait timeout exceeded</errortext>. + </para> + + <note> + <para> + This issue affected both in-memory and Disk Data tables. + </para> + </note> + + </message> + </logentry> <logentry entrytype="feature"> @@ -96852,35 +96317,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> - <manual type="print_data"/> - <manual type="ndb_restore"/> - </tags> - - <bugs> - <fixes bugid="26741"/> - <introducedby bugid="14612"/> - </bugs> - - <versions> - <version ver="5.1.15-ndb-6.1.4"/> - </versions> - - <message> - - <para> - Using only the <option>--print_data</option> option (and no - other options) with <command>ndb_restore</command> caused - <command>ndb_restore</command> to fail. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="replication"/> <manual type="Windows"/> <manual type="row-based logging"/> @@ -99496,6 +98932,7 @@ <versions> <version ver="5.1.19-ndb-6.2.3"/> + <version ver="5.1.20"/> </versions> <message> @@ -99934,6 +99371,8 @@ </bugs> <versions> + <version ver="5.1.15-ndb-6.1.16"/> + <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.21"/> </versions> @@ -100355,6 +99794,7 @@ <logentry entrytype="bug"> <tags> + <highlight type="cluster"/> <manual type="QMGR"/> </tags> @@ -100363,8 +99803,9 @@ </bugs> <versions> - <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.15-ndb-6.1.14"/> + <version ver="5.1.19-ndb-6.2.3"/> + <version ver="5.1.20"/> </versions> <message> @@ -101777,32 +101218,6 @@ <logentry entrytype="bug"> <tags> - <manual type="mysql_install_db"/> - </tags> - - <bugs> - <fixes bugid="30084"/> - </bugs> - - <versions> - <version ver="5.0.46"/> - </versions> - - <message> - - <para> - On the IBM i5 platform, the installation script in *SAVF - binaries unconditionally executed the - <command>mysql_install_db</command> script. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="UNION"/> <manual type="NULL"/> <manual type="SELECT"/> @@ -102506,31 +101921,6 @@ <logentry entrytype="bug"> <tags> - <manual type="BLOB"/> - </tags> - - <bugs> - <fixes bugid="29102"/> - </bugs> - - <versions> - <version ver="5.0.50"/> - </versions> - - <message> - - <para> - Reads on <literal>BLOB</literal> columns were not locked when - they needed to be, in order to guarantee consistency. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="INTEGER"/> <manual type="CHAR"/> </tags> @@ -103690,34 +103080,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> - <manual type="FLOAT"/> - <manual type="ndb_size.pl"/> - </tags> - - <bugs> - <fixes bugid="29228"/> - </bugs> - - <versions> - <version ver="5.1.22-ndb-6.2.5"/> - </versions> - - <message> - - <para> - <command>ndb_size.pl</command> failed on tables with - <literal>FLOAT</literal> columns whose definitions included - commas (for example, <literal>FLOAT(6,2)</literal>). - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="subqueries"/> </tags> @@ -103827,33 +103189,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="clusterapi"/> - <manual type="ndb_mgm_set_timeout"/> - </tags> - - <bugs> - <fixes bugid="29063"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - </versions> - - <message> - - <para> - The timeout set using the MGM API - <literal>ndb_mgm_set_timeout()</literal> function was - incorrectly interpreted as seconds rather than as milliseconds. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -104270,6 +103605,7 @@ <versions> <version ver="5.1.19-ndb-6.2.4"/> + <version ver="5.1.21"/> </versions> <message> @@ -105046,36 +104382,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="cluster"/> - <manual type="TEXT"/> - <manual type="BLOB"/> - <manual type="TRUNCATE"/> - </tags> - - <bugs> - <fixes bugid="19201"/> - </bugs> - - <versions> - <version ver="5.1.11"/> - </versions> - - <message> - - <para> - <literal>TRUNCATE</literal> failed on tables having - <literal>BLOB</literal> or <literal>TEXT</literal> columns with - the error <errortext>Lock wait timeout exceeded</errortext>. - This affected both in-memory and Disk Data tables. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -105527,36 +104833,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="replication"/> - <manual type="replication"/> - <manual type="DELETE"/> - <manual type="INSERT"/> - </tags> - - <bugs> - <fixes bugid="30914"/> - </bugs> - - <versions> - <version ver="5.1.15-ndb-6.1.20"/> - </versions> - - <message> - - <para> - Incorrect handling of <literal>INSERT</literal> plus - <literal>DELETE</literal> operations with regard to local - checkpoints caused data node failures in multi-master - replication setups. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -105575,7 +104851,7 @@ <message> <para> - <literal>InnoDB</literal>: Make <literal>CHECK TABLE</literal> + <literal>InnoDB</literal>: Made <literal>CHECK TABLE</literal> killable. </para> @@ -107167,28 +106443,6 @@ <logentry entrytype="bug"> - <bugs> - <fixes bugid="29354"/> - </bugs> - - <versions> - <version ver="5.1.15-ndb-6.1.17"/> - <version ver="5.1.19-ndb-6.2.4"/> - </versions> - - <message> - - <para> - Replica redo logs were inconsistently handled during a system - restart. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - <tags> <highlight type="cluster"/> <manual type="ndb_mgmd"/> @@ -107767,33 +107021,6 @@ <logentry entrytype="bug"> <tags> - <manual type="REDO"/> - </tags> - - <bugs> - <fixes bugid="29057"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - <version ver="5.1.15-ndb-6.1.16"/> - </versions> - - <message> - - <para> - If at least 2 files were involved in <literal>REDO</literal> - invalidation, then file 0 of page 0 was not updated and so - pointed to an invalid part of the redo log. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="MOD"/> <manual type="BIGINT"/> </tags> @@ -109233,34 +108460,6 @@ <logentry entrytype="bug"> <tags> - <manual type="transactions"/> - </tags> - - <bugs> - <fixes bugid="29804"/> - </bugs> - - <versions> - <version ver="5.0.48"/> - </versions> - - <message> - - <para> - Non-range queries of the form <literal>SELECT ... FROM ... WHERE - keypart_1=const, ..., keypart_n=const ORDER BY ... FOR - UPDATE</literal> sometimes were unneccesarily blocked waiting - for a lock if another transaction was using <literal>SELECT ... - FOR UPDATE</literal> on the same table. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="upgrade_defaults"/> <manual type="password"/> <manual type="mysql_upgrade"/> @@ -109628,6 +108827,7 @@ </bugs> <versions> + <version ver="5.1.22-ndb-6.2.5"/> <version ver="5.1.23"/> </versions> @@ -111094,35 +110294,6 @@ <logentry entrytype="bug"> <tags> - <highlight type="cluster"/> - <manual type="NULL"/> - <manual type="VARBINARY"/> - <manual type="ndb_restore"/> - </tags> - - <bugs> - <fixes bugid="29103"/> - </bugs> - - <versions> - <version ver="5.1.20"/> - </versions> - - <message> - - <para> - Attempting to restore a <literal>NULL</literal> row to a - <literal>VARBINARY</literal> column caused - <command>ndb_restore</command> to fail. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="STRICT"/> <manual type="ALTER TABLE"/> </tags> @@ -114708,32 +113879,7 @@ <logentry entrytype="bug"> - <tags> - <highlight type="cluster"/> - </tags> - <bugs> - <fixes bugid="29067"/> - </bugs> - - <versions> - <version ver="5.1.21"/> - </versions> - - <message> - - <para> - The wrong data pages were sometimes invalidated following a - global checkpoint. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <bugs> <fixes bugid="27954"/> </bugs> @@ -116330,32 +115476,6 @@ <logentry entrytype="bug"> <tags> - <manual type="DBTUP"/> - </tags> - - <bugs> - <fixes bugid="29229"/> - </bugs> - - <versions> - <version ver="5.1.19-ndb-6.2.3"/> - <version ver="5.1.15-ndb-6.1.15"/> - </versions> - - <message> - - <para> - Memory corruption could occur due to a problem in the - <literal>DBTUP</literal> kernel block. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="CONNECTION"/> </tags> @@ -119221,36 +118341,6 @@ </logentry> - <logentry entrytype="bug"> - - <tags> - <highlight type="cluster"/> - <manual type="QMGR"/> - </tags> - - <bugs> - <fixes bugid="29167"/> - </bugs> - - <versions> - <version ver="5.1.20"/> - </versions> - - <message> - - <para> - In the event that two data nodes in the same node group and - participating in a GCP crashed before they had written their - respective <filename>P0.sysfile</filename> files, - <literal>QMGR</literal> could refuse to start, issuing an - invalid <errortext>Insufficient nodes for restart</errortext> - error instead. - </para> - - </message> - - </logentry> - <logentry entrytype="feature"> <tags> @@ -121418,27 +120508,6 @@ <logentry entrytype="bug"> - <bugs> - <introducedby bugid="29354"/> - </bugs> - - <versions> - <version ver="5.1.15-ndb-6.1.18"/> - </versions> - - <message> - - <para> - A problem with the fix for Bug #29354 caused an assertion when - two local checkpoints were run during node recovery. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - <tags> <manual type="query"/> <manual type="mysqltest"/> @@ -125701,33 +124770,6 @@ <logentry entrytype="bug"> <tags> - <manual type="mysql_install_db"/> - </tags> - - <bugs> - <fixes bugid="30084"/> - </bugs> - - <versions> - <version ver="5.0.44"/> - </versions> - - <message> - - <para> - On the IBM i5 platform, the installation script in *SAVF - binaries unconditionally executed the - <command>mysql_install_db</command> script. This problem was - fixed in a repackaged distribution numbered 5.0.44b. - </para> - - </message> - - </logentry> - - <logentry entrytype="bug"> - - <tags> <manual type="mysqlcheck"/> </tags> @@ -127873,6 +126915,7 @@ </bugs> <versions> + <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.20"/> </versions> @@ -128997,6 +128040,8 @@ </bugs> <versions> + <version ver="5.1.15-ndb-6.1.16"/> + <version ver="5.1.19-ndb-6.2.3"/> <version ver="5.1.21"/> </versions> @@ -129005,7 +128050,7 @@ <para> When a node failed to respond to a <literal>COPY_GCI</literal> signal as part of a global checkpoint, the master node was - killed instead instead of the node that actually failed. + killed instead of the node that actually failed. </para> </message> @@ -133019,18 +132064,19 @@ </tags> <bugs> - <fixes bugid="29856"/> + <fixes bugid="30088"/> </bugs> <versions> + <version ver="5.0.48"/> <version ver="5.1.21"/> </versions> <message> <para> - <option>--myisam-recover=""</option> (empty option - value) did not disable <literal>MyISAM</literal> recovery. + <option>--myisam-recover=''</option> (empty option value) did + not disable <literal>MyISAM</literal> recovery. </para> </message>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r8800 - trunk/dynamic-docs/changelog | jon | 20 Nov |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.975 sec. using MySQL 5.1.14-beta-log