Author: mcbrown
Date: 2007-10-23 09:32:59 +0200 (Tue, 23 Oct 2007)
New Revision: 8250
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-23 00:39:21 UTC (rev 8249)
+++ trunk/dynamic-docs/open-bugs/mysqld.xml 2007-10-23 07:32:59 UTC (rev 8250)
Changed blocks: 16, Lines Added: 59, Lines Deleted: 437; 12220 bytes
@@ -285,43 +285,6 @@
</tags>
<bugs>
- <fixes bugid="21587"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>FLUSH TABLES</literal> causes server crash
- when used with <literal>HANDLER</literal> statements
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Using FLUSH TABLES in one connection while another
- connection is using HANDLER statements caused a server
- crash. Workaround: Avoid FLUSH TABLES while using HANDLER.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
<fixes bugid="21704"/>
</bugs>
@@ -934,76 +897,6 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="31069"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %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>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="31070"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %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>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server: Cluster"/>
</tags>
@@ -1033,6 +926,9 @@
of by the fix in 5.1.21 for Bug #21074, further analysis is
being done to determine if this is so.
</para>
+ <para>
+ <emphasis role="bold">Target fix</emphasis>: 5.1
+ </para>
</listitem>
</itemizedlist>
@@ -1073,6 +969,9 @@
(2, 4, 8, ...) and NumberOfReplicas should be equal to 1 or
2.
</para>
+ <para>
+ <emphasis role="bold">Target fix</emphasis>: 5.0
+ </para>
</listitem>
</itemizedlist>
@@ -1111,7 +1010,7 @@
detect this, which results in a lingering connection.
</para>
<para>
- <emphasis role="bold">Target fix</emphasis>: 5.1.23
+ <emphasis role="bold">Target fix</emphasis>: 5.1
</para>
</listitem>
@@ -1235,42 +1134,8 @@
write-locked with engine condition pushdown enabled. This
issue is not known to occur prior to MySQL 5.0.42.
</para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="30529"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>NDB</literal>'s write_row method doesn't set
- default values for columns not in write_set
- </para>
-
- <itemizedlist>
-
- <listitem>
<para>
- This issue manifests itself when, in Cluster replication, a
- table on the slave is created having extra columns as
- compared to the same table on the master.
+ <emphasis role="bold">Target fix</emphasis>: 5.0
</para>
</listitem>
@@ -1314,47 +1179,9 @@
statements creating Disk Data files whose size is greater
than 4 GB on 32-bit hosts.
</para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Compiling"/>
- </tags>
-
- <bugs>
- <fixes bugid="15327"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: configure: --with-tcp-port option being partially
- ignored
- </para>
-
- <itemizedlist>
-
- <listitem>
<para>
- Client programs are not respecting the TCP/IP port number
- specified via the --with-tcp-port configure option.
- Workaround: Specify --port=port_num explicitly when invoking
- clients.
+ <emphasis role="bold">Target fix</emphasis>: 5.1
</para>
- <para>
- <emphasis role="bold">Target fix</emphasis>: 5.1.23
- </para>
</listitem>
</itemizedlist>
@@ -1710,42 +1537,6 @@
</tags>
<bugs>
- <fixes bugid="16918"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Aborted_clients > Connections
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The Aborted_clients value could be incremented twice when a
- client exits without calling mysql_close(), resulting in an
- artificially high value.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
<fixes bugid="26180"/>
</bugs>
@@ -1935,44 +1726,6 @@
</tags>
<bugs>
- <fixes bugid="31035"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: select from function, group by result crasher
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- 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>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
<fixes bugid="31048"/>
</bugs>
@@ -2318,85 +2071,6 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server: Logging"/>
- </tags>
-
- <bugs>
- <fixes bugid="21557"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: entries in the general query log truncated at 1000
- characters.
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Long statements written to the general query log might be
- truncated. One effect is that statements cannot be
- copied-and-pasted to re-execute them. There is currently no
- workaround.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Memory"/>
- </tags>
-
- <bugs>
- <fixes bugid="30590"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: delete from memory table with composite btree primary
- key
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Using a MEMORY table where the primary key is a compound key
- using two or more colums and btree indexing results in some
- 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>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server: Merge"/>
</tags>
@@ -2544,6 +2218,16 @@
server to crash
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ See description for Bug #26379.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
</message>
</logentry>
@@ -2830,44 +2514,6 @@
</tags>
<bugs>
- <fixes bugid="30583"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Partition on <literal>DOUBLE</literal> key +
- <literal>INNODB</literal> + count(*) == crash
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The issue arises with a COUNT() query on an InnoDB table
- using PARTITION BY KEY(double_column). It does not occur
- with MyISAM tables. A fix has been committed and is expected
- to be part of 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Partition"/>
- </tags>
-
- <bugs>
<fixes bugid="30695"/>
</bugs>
@@ -3298,6 +2944,43 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
+ <manual type="Server: RBR"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="30529"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1"/>
+ </versions>
+
+ <message>
+
+ <para>
+ %BUGID%: write_set not set correctly for columns with default
+ values
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ This issue manifests itself when, in Cluster replication, a
+ table on the slave is created having extra columns as
+ compared to the same table on the master.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="custom" customname="open-bugs">
+
+ <tags>
<manual type="Server: Replication"/>
</tags>
@@ -3561,6 +3244,9 @@
event is later received by a different SQL node in the same
cluster.
</para>
+ <para>
+ <emphasis role="bold">Target fix</emphasis>: 6.0
+ </para>
</listitem>
</itemizedlist>
@@ -3712,30 +3398,6 @@
</tags>
<bugs>
- <fixes bugid="28772"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: rpl_row_until fails in pushbuild
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
<fixes bugid="29288"/>
</bugs>
@@ -4261,46 +3923,6 @@
</tags>
<bugs>
- <fixes bugid="29804"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>UDF</literal> parameters don't contain correct
- string length
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Under some circumstances, a UDF initialization function
- 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>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: UDF"/>
- </tags>
-
- <bugs>
<fixes bugid="30503"/>
</bugs>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8250 - trunk/dynamic-docs/open-bugs | mcbrown | 23 Oct |
