| List: | Commits | « Previous MessageNext Message » | |
| From: | mcbrown | Date: | October 21 2007 1:00am |
| Subject: | svn commit - mysqldoc@docsrva: r8228 - trunk/dynamic-docs/open-bugs | ||
| View as plain text | |||
Author: mcbrown Date: 2007-10-21 01:00:10 +0200 (Sun, 21 Oct 2007) New Revision: 8228 Log: Automatic update from openbugs Modified: trunk/dynamic-docs/open-bugs/mysqld.xml Modified: trunk/dynamic-docs/open-bugs/mysqld.xml =================================================================== --- trunk/dynamic-docs/open-bugs/mysqld.xml 2007-10-20 18:21:31 UTC (rev 8227) +++ trunk/dynamic-docs/open-bugs/mysqld.xml 2007-10-20 23:00:10 UTC (rev 8228) Changed blocks: 160, Lines Added: 135, Lines Deleted: 750; 46175 bytes @@ -5,21 +5,15 @@ <logentry entrytype="custom" customname="open-bugs" customtitle="The following problems are known and fixing them is a high priority:"> <tags> - <manual type="C API"/> - </tags> <bugs> - <fixes bugid="29605"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -29,6 +23,21 @@ <literal>FETCH LOCAL FILE</literal> response </para> + <itemizedlist> + + <listitem> + <para> + --local-infile=0 disables support for LOAD LOCAL INFILE in + MySQL clients. However, this is currently enforced only on + the server, which means that a "fake" server (that is, one + that disregards the --local-infile setting) can read any + files to which clients have access. It is assumed that this + issue affects all MySQL client libraries and applications. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -36,21 +45,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="C API"/> - </tags> <bugs> - <fixes bugid="30472"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -81,21 +84,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Client"/> - </tags> <bugs> - <fixes bugid="25162"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -127,21 +124,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Client"/> - </tags> <bugs> - <fixes bugid="30679"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -159,7 +150,6 @@ for views when upgrading from 5.0 to 5.1. Workaround: Drop and recreate affected views. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -174,21 +164,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Client"/> - </tags> <bugs> - <fixes bugid="30946"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -221,21 +205,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Connector/J"/> - </tags> <bugs> - <fixes bugid="20491"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -245,6 +223,20 @@ DatabaseMetaData.getColumns() </para> + <itemizedlist> + + <listitem> + <para> + If a table column name contains German umlauts, the method + DatabaseMetaData.getColumns() returns a ResultSet that + contains unusable column names. This issue is known to occur + using Connector/J 3.1 or newer. Workaround: Use a version of + the Connector previous to 3.1. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -252,21 +244,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="21476"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -295,21 +281,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="21587"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -338,21 +318,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="21704"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -386,21 +360,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="22351"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -418,7 +386,6 @@ columns for both the primary key and the partitioning can return the wrong number of rows. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1 </para> @@ -433,21 +400,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="22563"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -474,21 +435,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="23590"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -520,21 +475,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="25874"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -562,21 +511,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="28543"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -605,21 +548,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="29419"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -651,21 +588,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="29553"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -684,7 +615,6 @@ Windows page file, or to decrease the amount of physical memory on the machine. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 6.0 </para> @@ -699,21 +629,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="29908"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -732,7 +656,6 @@ privileges. The fix will be to allow only the original view definer to alter the view. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -747,21 +670,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="30355"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -777,7 +694,6 @@ Under some circumstances, a UDF initialization function could be passed incorrect argument lengths. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -792,21 +708,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="30897"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -835,21 +745,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server"/> - </tags> <bugs> - <fixes bugid="31036"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -878,21 +782,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Backup"/> - </tags> <bugs> - <fixes bugid="20786"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -921,21 +819,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Charsets"/> - </tags> <bugs> - <fixes bugid="29562"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -965,21 +857,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Charsets"/> - </tags> <bugs> - <fixes bugid="30981"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1008,21 +894,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Charsets"/> - </tags> <bugs> - <fixes bugid="30982"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1053,21 +933,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Charsets"/> - </tags> <bugs> - <fixes bugid="30986"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1097,21 +971,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Charsets"/> - </tags> <bugs> - <fixes bugid="31069"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1120,6 +988,17 @@ %BUGID%: crash in 'sounds like' </para> + <itemizedlist> + + <listitem> + <para> + A fix for this issue has been committed and is expected to + appear in MySQL 5.1.23. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -1127,21 +1006,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Charsets"/> - </tags> <bugs> - <fixes bugid="31070"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1150,6 +1023,17 @@ %BUGID%: crash during conversion of charsets </para> + <itemizedlist> + + <listitem> + <para> + A fix for this issue has been committed and is expected to + appear in MySQL 5.1.23. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -1157,21 +1041,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Cluster"/> - </tags> <bugs> - <fixes bugid="19144"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1203,21 +1081,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Cluster"/> - </tags> <bugs> - <fixes bugid="24763"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1249,21 +1121,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Cluster"/> - </tags> <bugs> - <fixes bugid="28445"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1281,7 +1147,6 @@ occurs, there is a short interval before data nodes can detect this, which results in a lingering connection. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -1296,21 +1161,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Cluster"/> - </tags> <bugs> - <fixes bugid="28647"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1330,7 +1189,6 @@ issue has been committed and is expected to appear in the next 5.1 release. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -1345,21 +1203,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Cluster"/> - </tags> <bugs> - <fixes bugid="29390"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1378,7 +1230,6 @@ fixed in MySQL Cluster Carrier Grade Edition (MySQL 5.1.22-ndb-6.3.4). </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -1393,21 +1244,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Cluster"/> - </tags> <bugs> - <fixes bugid="30407"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1438,21 +1283,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Cluster"/> - </tags> <bugs> - <fixes bugid="30529"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1481,21 +1320,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: ClusterDD"/> - </tags> <bugs> - <fixes bugid="29186"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1529,21 +1362,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Compiling"/> - </tags> <bugs> - <fixes bugid="15327"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1562,7 +1389,6 @@ Workaround: Specify --port=port_num explicitly when invoking clients. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -1577,21 +1403,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Compiling"/> - </tags> <bugs> - <fixes bugid="17612"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1618,21 +1438,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Compiling"/> - </tags> <bugs> - <fixes bugid="30296"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1660,21 +1474,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: DDL"/> - </tags> <bugs> - <fixes bugid="15187"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1701,21 +1509,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: DDL"/> - </tags> <bugs> - <fixes bugid="17565"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1733,7 +1535,6 @@ being removed and replaced with ALTER TABLE db_name UPGRADE DATA DIRECTORY NAME. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -1748,21 +1549,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: DDL"/> - </tags> <bugs> - <fixes bugid="28360"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1780,7 +1575,6 @@ being removed and replaced with ALTER TABLE db_name UPGRADE DATA DIRECTORY NAME. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -1795,21 +1589,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: DML"/> - </tags> <bugs> - <fixes bugid="27358"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1839,52 +1627,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - - <manual type="Server: Docs"/> - - </tags> - - <bugs> - - <fixes bugid="30577"/> - - </bugs> - - <versions> - - <version ver="5.1"/> - - </versions> - - <message> - - <para> - %BUGID%: <literal>FLOOR</literal>() and - <literal>CEILING</literal>() not usable as partition functions - </para> - - </message> - - </logentry> - - <logentry entrytype="custom" customname="open-bugs"> - - <tags> - <manual type="Server: Events"/> - </tags> <bugs> - <fixes bugid="31111"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1901,7 +1652,6 @@ server at startup. Workaround: Do not use --read-only, or disable the Event Manager with --event-scheduler=0. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -1916,21 +1666,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Federated"/> - </tags> <bugs> - <fixes bugid="30671"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1959,21 +1703,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="5731"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -1991,7 +1729,6 @@ high on a 32-bit operating system. The fix will appear in 5.1.23. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -2006,21 +1743,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="16918"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2048,21 +1779,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="26180"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2094,21 +1819,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="28687"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2136,21 +1855,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="30825"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2180,21 +1893,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="30889"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2224,21 +1931,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="30942"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2267,21 +1968,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="31035"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2297,7 +1992,6 @@ The optimizer did not properly handle stored functions in ORDER BY clauses and the server could crash. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.0.50,5.1 </para> @@ -2312,21 +2006,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="31048"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2355,21 +2043,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: General"/> - </tags> <bugs> - <fixes bugid="31081"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2396,21 +2078,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: InnoDB"/> - </tags> <bugs> - <fixes bugid="29157"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2442,21 +2118,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Installing"/> - </tags> <bugs> - <fixes bugid="24853"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2476,7 +2146,6 @@ an exception for port 3306 to the Windows Wista firewall manually. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1 </para> @@ -2491,21 +2160,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Installing"/> - </tags> <bugs> - <fixes bugid="28628"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2518,6 +2181,12 @@ <listitem> <para> + During the Security Settings phase, a Connection Error can + occur because the installer tries to proceed before the + MySQL Server being installed is fully started. Workaround: + wait a few moments, then click Retry in the error dialog. + </para> + <para> <emphasis role="bold">Target fix</emphasis>: 5.1 </para> </listitem> @@ -2531,21 +2200,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Installing"/> - </tags> <bugs> - <fixes bugid="30487"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2575,21 +2238,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Installing"/> - </tags> <bugs> - <fixes bugid="30916"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2617,21 +2274,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: I_S"/> - </tags> <bugs> - <fixes bugid="19588"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2652,7 +2303,6 @@ possible. Note: A patch for this issue has been committed since the 5.1.22 release. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -2667,21 +2317,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: I_S"/> - </tags> <bugs> - <fixes bugid="30689"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2711,21 +2355,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Logging"/> - </tags> <bugs> - <fixes bugid="21557"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2755,21 +2393,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Memory"/> - </tags> <bugs> - <fixes bugid="30590"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2788,7 +2420,6 @@ rows not being deleted when the statement specifies only a single column from the primary key index. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -2803,21 +2434,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Merge"/> - </tags> <bugs> - <fixes bugid="26377"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2838,7 +2463,6 @@ Specifying the MYISAM table before the MERGE table does not cause the same problem. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -2853,21 +2477,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Merge"/> - </tags> <bugs> - <fixes bugid="26379"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2889,7 +2507,6 @@ merge table. A fix for this bug has been prepared and is expected to appear in 5.1.23. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -2904,21 +2521,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Merge"/> - </tags> <bugs> - <fixes bugid="26867"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2938,7 +2549,6 @@ INSERT statement on the same table is waiting on another connection causes signficant CPU/memory usage. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -2953,21 +2563,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Merge"/> - </tags> <bugs> - <fixes bugid="30275"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -2984,21 +2588,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: MyISAM"/> - </tags> <bugs> - <fixes bugid="29446"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3030,21 +2628,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: MyISAM"/> - </tags> <bugs> - <fixes bugid="30286"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3076,21 +2668,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: MyISAM"/> - </tags> <bugs> - <fixes bugid="30638"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3108,7 +2694,6 @@ MYISAM table on windows, the row count is reset to 0. The data in the table is still accessible. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -3123,21 +2708,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Optimizer"/> - </tags> <bugs> - <fixes bugid="31075"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3165,21 +2744,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Optimizer"/> - </tags> <bugs> - <fixes bugid="31094"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3199,7 +2772,6 @@ enforced even when a LIMIT clause was given, when the rule should not apply. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -3214,21 +2786,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Partition"/> - </tags> <bugs> - <fixes bugid="29258"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3261,21 +2827,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Partition"/> - </tags> <bugs> - <fixes bugid="30573"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3303,21 +2863,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Partition"/> - </tags> <bugs> - <fixes bugid="30583"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3347,21 +2901,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Partition"/> - </tags> <bugs> - <fixes bugid="30695"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3378,7 +2926,6 @@ A patch has been committed for this issue and is expected to appear in 5.1.23 or 5.1.24. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1 </para> @@ -3393,21 +2940,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Partition"/> - </tags> <bugs> - <fixes bugid="30822"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3435,21 +2976,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Privileges"/> - </tags> <bugs> - <fixes bugid="30468"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3467,7 +3002,6 @@ table access for both tables in the join was done using the grant information of the first table </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -3482,21 +3016,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: PS"/> - </tags> <bugs> - <fixes bugid="27430"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3517,7 +3045,6 @@ completely disallow prepared statements by setting the system variable max_prepared_stmt_count to 0. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 6.0 </para> @@ -3532,21 +3059,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: PS"/> - </tags> <bugs> - <fixes bugid="27690"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3566,7 +3087,6 @@ completely disallow prepared statements by setting the system variable max_prepared_stmt_count to 0. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 6.0 </para> @@ -3581,21 +3101,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Query Cache"/> - </tags> <bugs> - <fixes bugid="30768"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3623,21 +3137,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: RBR"/> - </tags> <bugs> - <fixes bugid="19958"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3664,21 +3172,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: RBR"/> - </tags> <bugs> - <fixes bugid="26366"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3707,21 +3209,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: RBR"/> - </tags> <bugs> - <fixes bugid="27779"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3751,21 +3247,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: RBR"/> - </tags> <bugs> - <fixes bugid="29020"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3785,7 +3275,6 @@ The fix for this issue depends on the fix for Bug #12713, which is expected in 5.1.23. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -3800,21 +3289,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: RBR"/> - </tags> <bugs> - <fixes bugid="29549"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3828,6 +3311,17 @@ <listitem> <para> + Row-based logging writes rows incorrectly on big-endian + machines where the storage engine sets the low byte first on + big-endian machines, while little-endian machines write the + fields in correct order. (The only known storage engine that + does this is NDB.) In effect, this means that row-based + replication from or to a big-endian machine where the table + uses NDB as storage engine fails if the other engine is + either non-NDB or on a little-endian machine. A fix for this + issue has been committed to 5.1.23. + </para> + <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> </listitem> @@ -3841,21 +3335,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="21132"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3871,21 +3359,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="23333"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3908,7 +3390,6 @@ not have. A fix for this issue is pending; it is expected to appear in 5.1.23. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -3923,21 +3404,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="26000"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -3969,21 +3444,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="26199"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4000,7 +3469,6 @@ The workaround is to use parameters of INT types rather than BIT type. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1 </para> @@ -4015,21 +3483,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="26395"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4066,21 +3528,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="26489"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4114,21 +3570,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="27808"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4159,21 +3609,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="27991"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4190,21 +3634,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="28086"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4232,21 +3670,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="28597"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4274,21 +3706,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="28618"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4305,7 +3731,6 @@ A fix for this issue has been committed and is expected to be included in MySQL 5.1.23. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -4320,21 +3745,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="28772"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4350,21 +3769,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="29288"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4395,21 +3808,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="29309"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4429,7 +3836,6 @@ incorrectly. This can cause false alerts for monitoring services. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -4444,21 +3850,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="29563"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4468,6 +3868,21 @@ when charset=ucs2 </para> + <itemizedlist> + + <listitem> + <para> + If you set --default-collation=ucs2_general_ci on the + master, and then use mysqlbinlog to print the binary log + (and pipe it into mysql client) it sets the client charset + to UCS2 and then sends the statement SET + @@session.character_set_client...; using the latin1 + character set. (See also Bug #29562.) + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -4475,21 +3890,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="29564"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4499,6 +3908,18 @@ ucs2_general_ci </para> + <itemizedlist> + + <listitem> + <para> + When using the ucs_general_ci collation with row-based + replication, BEGIN and COMMIT statements are inserted into + the binary log using an incorrect character set. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -4506,21 +3927,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="29734"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4530,6 +3945,21 @@ table conflicts </para> + <itemizedlist> + + <listitem> + <para> + In some cases, the binary log generated on the master can + have thread_id=0, possibly for multiple threads. Normally, + this does not matter; however, where two threads use the + same temporary table, the pseudo_thread_id is also set to 0, + and causing conflicts which interfere with replication and + point-in-time recovery. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -4537,21 +3967,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="30209"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4577,21 +4001,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="30752"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4601,6 +4019,20 @@ uninitialized <literal>LOG_INFO</literal>) </para> + <itemizedlist> + + <listitem> + <para> + One thread in the MySQL replication code can read + uninitialized memory from the stack of another thread. This + appears to be strictly an internal issue; a fix has been + prepared and is expected to be committed to the server code + in time for MySQL 5.1.23 or 5.1.24. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -4608,21 +4040,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="30790"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4648,21 +4074,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Replication"/> - </tags> <bugs> - <fixes bugid="30854"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4679,21 +4099,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: SP"/> - </tags> <bugs> - <fixes bugid="12713"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4714,7 +4128,6 @@ problem with scheduled events encountered in Bug #29020. A fix for this issue is expected in 5.1.23. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -4729,21 +4142,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Tests"/> - </tags> <bugs> - <fixes bugid="29290"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4758,7 +4165,6 @@ <para> Date-based test fails when run at midnight. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1 </para> @@ -4773,21 +4179,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Types"/> - </tags> <bugs> - <fixes bugid="24541"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4808,7 +4208,6 @@ users being adversely affected by unanticipated changes in behaviour. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 6.0 </para> @@ -4823,21 +4222,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Types"/> - </tags> <bugs> - <fixes bugid="30587"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4866,21 +4259,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: Types"/> - </tags> <bugs> - <fixes bugid="30955"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4889,6 +4276,17 @@ %BUGID%: geomfromtext() crasher </para> + <itemizedlist> + + <listitem> + <para> + A fix has been written for this issue and is expected to + appear in MySQL 5.1.23 or 5.1.24. + </para> + </listitem> + + </itemizedlist> + </message> </logentry> @@ -4896,21 +4294,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: UDF"/> - </tags> <bugs> - <fixes bugid="29804"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message> @@ -4928,7 +4320,6 @@ could be passed incorrect argument lengths. A fix for this issue is expected in 5.1.23. </para> - <para> <emphasis role="bold">Target fix</emphasis>: 5.1.23 </para> @@ -4943,21 +4334,15 @@ <logentry entrytype="custom" customname="open-bugs"> <tags> - <manual type="Server: UDF"/> - </tags> <bugs> - <fixes bugid="30503"/> - </bugs> <versions> - <version ver="5.1"/> - </versions> <message>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r8228 - trunk/dynamic-docs/open-bugs | mcbrown | 21 Oct |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 1.022 sec. using MySQL 5.1.14-beta-log