Author: mcbrown
Date: 2008-07-16 08:51:55 +0200 (Wed, 16 Jul 2008)
New Revision: 11266
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 2008-07-16 02:18:26 UTC (rev 11265)
+++ trunk/dynamic-docs/open-bugs/mysqld.xml 2008-07-16 06:51:55 UTC (rev 11266)
Changed blocks: 8, Lines Added: 0, Lines Deleted: 5662; 107266 bytes
@@ -5,536 +5,10 @@
<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"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: --local-infile=0 checks can be bypassed by sending a
- <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>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="C API"/>
- </tags>
-
- <bugs>
- <fixes bugid="30472"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: libmysql doesn't reset charset, insert_id after succ.
- mysql_change_user() call
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- After mysql_change_user(), the character set variables
- should be just as after mysql_real_connect(). However, the
- server sets them to the global defaults. A workaround would
- be to explicitly reinitialize character set information
- explicitly following mysql_change_user().
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="C API"/>
- </tags>
-
- <bugs>
- <fixes bugid="34655"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Compile error
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Client"/>
- </tags>
-
- <bugs>
- <fixes bugid="26215"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysql command line client should not strip comments
- from <literal>SQL</literal> statements
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Client"/>
- </tags>
-
- <bugs>
- <fixes bugid="32221"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: bug25714, mytest, mysql_client_test complaints and
- crashes
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Client"/>
- </tags>
-
- <bugs>
- <fixes bugid="33057"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysql command line client slows down and uses 100%
- <literal>CPU</literal> when restoring dump
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Client"/>
- </tags>
-
- <bugs>
- <fixes bugid="33841"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="4.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysql client crashes when returning results for long
- running queries
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="libmysqld"/>
- </tags>
-
- <bugs>
- <fixes bugid="30430"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: crash: ./mtr --embeded-server --ps-protocol
- cache_innodb func_misc ...
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="libmysqld"/>
- </tags>
-
- <bugs>
- <fixes bugid="31868"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysql_server_init crash when language path is not
- correctly set
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="libmysqld"/>
- </tags>
-
- <bugs>
- <fixes bugid="32063"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: "create table like" works case-significant only in
- "embedded" server (libmysqld)
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="libmysqld"/>
- </tags>
-
- <bugs>
- <fixes bugid="32624"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Error with multi queries in MySQL Embedded Server
- 5.1.22
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server"/>
</tags>
<bugs>
- <fixes bugid="19723"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.?"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>KILL</literal> of active connection yields
- error on Mac <literal>OS</literal> X
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="22351"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: handler::index_next_same() call to key_cmp_if_same()
- uses the wrong buffer
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Queries against tables partioned by key using multiple
- columns for both the primary key and the partitioning can
- return the wrong number of rows.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="24907"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: unpredictable (display) precision, if input precision
- increases
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="26447"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: "<literal>ALTER TABLE</literal> ..
- <literal>ORDER</literal>" does not work with InnoDB and
- auto_increment keys
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="26788"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysqld (debug) aborts when inserting specific numbers
- into char fields
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="27545"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>NAME_CONST</literal>() fails to return
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
<fixes bugid="27848"/>
</bugs>
@@ -562,1326 +36,10 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="29419"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Specifying a join_buffer > 4GB on 64 bit machines
- not possible.
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- On 64-bit systems, specifying a join_buffer size greater
- than 4GB would cause the value to wrap on the 4GB boundary.
- For example, a join_buffer of 5GB would actually only
- reserve 1GB. On 64-bit systems this restriction will be
- lifted. On 32-bit systems, the join_buffer size will be
- limited to 4GB.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="29908"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: alter view keeps current definer, user can gain
- additioanl access
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- If a user changed a view with ALTER VIEW, the original
- DEFINER was retained, possibly allowing the new user to gain
- privileges. The fix will be to allow only the original view
- definer to alter the view.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="30152"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: MySQLD crash duing alter table causes <literal>DROP
- DATABASE</literal> to <literal>FAIL</literal> due to temp file
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="30355"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Incorrect ordering of <literal>UDF</literal> results
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Under some circumstances, a UDF initialization function
- could be passed incorrect argument lengths.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="30384"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>SQL_BUFFER_RESULT</literal> corrups indexes
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="30435"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: loading large <literal>LOAD DATA INFILE</literal>
- breaks slave with read_buffer_size set on master
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="30788"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Inconsistent retrieval of char/varchar
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="30897"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>GROUP_CONCAT</literal> returns extra comma on
- empty fields
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- For a column that contains only empty strings,
- GROUP_CONCAT() returns "," rather than the correct result of
- "".
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="31036"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Using order by with archive table crashes server
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Using ORDER BY as a clause within a SELECT on an archive
- table where the combined column length of the table is 510
- bytes or larger triggers. the crash. One workaround is to
- use a subselect on the query.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="31153"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: calling stored procedure crashes server if available
- memory is low
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="31177"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Server variables can't be set to their current values
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="32036"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>EXISTS</literal> within a
- <literal>WHERE</literal> clause with a <literal>UNION</literal>
- crashes MySQL 5.122
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="32051"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>UNION</literal> within
- <literal>EXISTS</literal> returns incorrect result
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="32268"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Indexed queries give bogus <literal>MIN</literal> and
- <literal>MAX</literal> results
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="32335"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: inconsistent int > null +1 behavior
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="32533"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>SELECT INTO</literal>/<literal>LOAD DATA
- INFILE</literal> with <literal>FIELDS ENCLOSED BY</literal> 8bit
- char corrupts data
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="32775"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: problems with <literal>SHOW EVENTS</literal> and
- Information_Schema
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="32798"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>DISTINCT</literal> in
- <literal>GROUP_CONCAT</literal> clause fails when ordering by a
- column with null values
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="33507"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Event scheduler creates more threads than
- max_connections = user lockout
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="33814"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Pre-auth buffer-overflow in mySQL through yaSSL
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="34749"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Server crash when using <literal>NAME_CONST</literal>()
- with an aggregate function
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="35074"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: max_used_connections is not correct
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server"/>
- </tags>
-
- <bugs>
- <fixes bugid="35732"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.24"/>
- <fixedin ver="5.1.25"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: read-only blocks <literal>SELECT</literal> statements
- in InnoDB
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="30981"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>CHAR</literal>(0x41 <literal>USING</literal>
- ucs2) doesn't add leading zero
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- CHAR(str USING ucs2) for strings with an odd number of bytes
- did not add a leading 0x00 byte. Workaround: Provide an
- even-length string.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="30982"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>CHAR</literal>(..<literal>USING</literal>..)
- can return a not-well-formed string
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- For CHAR(str USING charset) and CONVERT(str USING charset),
- no check was made that the string contained valid input for
- the character set (for example, CHAR(0xFF USING utf8) is
- invalid). An error should occur if the input is not
- well-formed.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="30986"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Character set introducer followed by a
- <literal>HEX</literal> string can return bad result
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- For a character set introducer followed by a hex string, no
- check was made that the string contained valid input for the
- character set (for example, _utf8 0xFF is invalid). An error
- should occur if the input is not well-formed.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="31069"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </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"/>
- <fixedin ver="5.1.23"/>
- </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: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="31615"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: crash after set names ucs2 collate xxx
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Charsets"/>
- </tags>
-
- <bugs>
- <fixes bugid="32726"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: crash with cast in order by clause and cp932 charset
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="28445"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Heartbeat does not start until first
- <literal>API_REGREQ</literal> is recevied
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- If an API or management node restarts or a network failure
- occurs, there is a short interval before data nodes can
- detect this, which results in a lingering connection.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="29390"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: too complex interpreted program crashes data nodes
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Interpeted NDB API programs of sufficient size and
- complexity can in some cases cause data nodes to shut down
- due to buffer overruns. Note: This issue has already been
- fixed in MySQL Cluster Carrier Grade Edition (MySQL
- 5.1.22-ndb-6.3.4).
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="30366"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>NDB</literal> fails to start on
- <literal>OS</literal> X, 64 bit
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Cluster"/>
- </tags>
-
- <bugs>
- <fixes bugid="33168"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Incorrectly handled parameters can make the
- <literal>TC</literal> crash during node failure
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: ClusterRep"/>
- </tags>
-
- <bugs>
- <fixes bugid="31484"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Cluster <literal>LOST_EVENTS</literal> entry not added
- to binlog on mysqld restart.
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- If the master mysqld node disconnects and reconnects to the
- cluster (for example, if the network connection is broken
- then re-established), a LOST_EVENTS entry is added to the
- binlog. However, when the master mysqld node crashes or has
- a normal restart it does not create the LOST_EVENTS entry.
- (This has already been fixed in MySQL Cluster Carrier Grade
- Edition releases 5.1.22-ndb-6.2.8 and 5.1.22-ndb-6.3.6.)
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: ClusterRep"/>
- </tags>
-
- <bugs>
- <fixes bugid="31958"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: many parallell create/delete ndb may hang ndbapi
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Under certain conditions, the slave may stop processing
- relay logs, which results in the logs never being cleared
- and the slave eventually running out of disk space. (Note:
- This issue has already been fixed in MySQL Cluster Carrier
- Grade versions 5.1.15-ndb-6.1.23 and 5.1.22-ndb-6.2.9.)
- </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"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </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.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Compiling"/>
- </tags>
-
- <bugs>
- <fixes bugid="18322"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Explicit link to libmtmalloc breaks dlopen()
- applications like <literal>DBD</literal>::mysql
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Compiling"/>
- </tags>
-
- <bugs>
- <fixes bugid="21158"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysql_config doesn't include -lmygcc
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Compiling"/>
- </tags>
-
- <bugs>
- <fixes bugid="30296"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Dynamic plugins fail to load on FreeBSD
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- (Apparent) workaround: ELF executables need to be linked
- using the -export-dynamic option to ld(1) for symbols
- defined in the executable to become visible to dlsym().
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Compiling"/>
- </tags>
-
- <bugs>
<fixes bugid="32179"/>
</bugs>
@@ -1902,310 +60,10 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server: CSV"/>
- </tags>
-
- <bugs>
- <fixes bugid="32050"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: table logging gone wrong.
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: CSV"/>
- </tags>
-
- <bugs>
- <fixes bugid="32817"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: though <literal>CSV</literal> is marked as supported
- create table is rejected with error 1005.
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DDL"/>
- </tags>
-
- <bugs>
- <fixes bugid="17565"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>RENAME DATABASE</literal> destroys events
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- RENAME DATABASE was intended only for updating names of
- pre-5.1 databases to the new 5.1 identifier encoding. It's
- being removed and replaced with ALTER TABLE db_name UPGRADE
- DATA DIRECTORY NAME.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DDL"/>
- </tags>
-
- <bugs>
- <fixes bugid="28360"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>RENAME DATABASE</literal> destroys routines
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- RENAME DATABASE was intended only for updating names of
- pre-5.1 databases to the new 5.1 identifier encoding. It is
- being removed and replaced with ALTER TABLE db_name UPGRADE
- DATA DIRECTORY NAME.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DDL"/>
- </tags>
-
- <bugs>
- <fixes bugid="30217"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Views: changes in metadata behaviour between 5.0 and
- 5.1
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DDL"/>
- </tags>
-
- <bugs>
- <fixes bugid="32158"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Crash in open_table_from_share, on
- mysql_unpack_partition errors
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DDL"/>
- </tags>
-
- <bugs>
- <fixes bugid="32633"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Can not create any routine if
- <literal>SQL_MODE</literal>=no_engine_substitution
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server: DML"/>
</tags>
<bugs>
- <fixes bugid="27358"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>INSERT DELAYED</literal> does not honour
- <literal>SQL_MODE</literal> of the client
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The SQL_MODE setting is ignored when a client issues INSERT
- DELAYED. A patch for this bug has been approved for MySQL
- 5.0, and is expected to be committed to 5.1 in the near
- future.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DML"/>
- </tags>
-
- <bugs>
- <fixes bugid="30234"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Unexpected behavior using <literal>DELETE</literal>
- with <literal>AS</literal> and <literal>USING</literal>
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DML"/>
- </tags>
-
- <bugs>
<fixes bugid="30776"/>
</bugs>
@@ -2227,698 +85,10 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server: DML"/>
- </tags>
-
- <bugs>
- <fixes bugid="32030"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>DELETE</literal> does not return an error and
- deletes rows if error evaluating <literal>WHERE</literal>
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: DML"/>
- </tags>
-
- <bugs>
- <fixes bugid="32482"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: crash with <literal>GROUP BY</literal>
- alias_of_user_variable <literal>WITH ROLLUP</literal>
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Events"/>
- </tags>
-
- <bugs>
- <fixes bugid="22738"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Events: After stop and start disabled events could
- reside in the queue
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Events"/>
- </tags>
-
- <bugs>
- <fixes bugid="27407"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Events: altering changes 'on completion preserve'
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Events"/>
- </tags>
-
- <bugs>
- <fixes bugid="31539"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>ALTER EVENT RENAME TO</literal>... resets
- <literal>STATUS</literal> to '<literal>ENAMLE</literal>'
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Federated"/>
- </tags>
-
- <bugs>
- <fixes bugid="30671"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>ALTER SERVER</literal> causes the Server to
- crash.
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Issuing an ALTER SERVER statement to modify an existing
- SERVER specification as used by the Federated storage engine
- causes the server to crash.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server: General"/>
</tags>
<bugs>
- <fixes bugid="5731"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: key_buffer_size not properly restricted to 4GB
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- This issue affects 32-bit platforms only. A fix has been
- committed that will prevent this buffer from being set too
- high on a 32-bit operating system. The fix will appear in
- 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="16918"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </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="20901"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>CREATE</literal> privilege is enough to insert
- into a table
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="28687"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Search fails on '0000-00-00' date after sql_mode change
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Indexed and non-indexed searches for '0000-00-00' return
- different results after inserting '0000-00-00' and then
- setting the SQL mode to TRADITIONAL.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="30763"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Multi-table <literal>UPDATE</literal> with transaction
- + non-transactional table assertion failure
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="30825"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Problems when putting a non-spatial index on a
- <literal>GIS</literal> column
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- For a spatial column with a regular (non-SPATIAL) index,
- queries failed if the optimizer tried to use the index.
- Workaround: Use IGNORE INDEX or remove the index (queries
- may be slow but will work).
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="30889"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: filesort and order by with float/numeric crashes server
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The implementation of ROUND() for DECIMAL/NUMERIC arguments
- could produce results where scale > precision, or where
- scale larger than the maximum allowable scale. One symptom
- is a crash when ORDER BY refers to an expression with
- ROUND().
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="30942"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: select str_to_date from derived table returns varying
- results
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- When invoked with constant arguments, STR_TO_DATE() could
- use a cached value for the format string and return
- incorrect results.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="30960"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: processlist state '*** <literal>DEAD</literal> ***' on
- recent 5.0.48 windows builds
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="31081"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: server crash in regexp function
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Using REGEX with ucs2 strings could cause a server crash.
- Workaround: Use an 8-bit character set if possible.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="31137"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Assertion failed: primary_key_no == -1 ||
- primary_key_no == 0, file .\ha_innodb.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="31745"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysqld crash handler does not work on windows
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="31747"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Valgrind error in replication tree because engines does
- not set all null bits
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="31928"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Search fails on '1000-00-00' date after sql_mode change
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="32374"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: crash with filesort when selecting from federated table
- and view
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
<fixes bugid="32543"/>
</bugs>
@@ -2940,173 +110,10 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server: General"/>
- </tags>
-
- <bugs>
- <fixes bugid="32559"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: connection hangs on query with name_const
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: InnoDB"/>
- </tags>
-
- <bugs>
- <fixes bugid="31540"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: incorrect auto_increment values used for multi-row
- insert trigger
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server: Installing"/>
</tags>
<bugs>
- <fixes bugid="24853"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Default port not added to Vista firewall exceptions
- list
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The effect of this bug is that remote access cannot be
- enabled automatically for MySQL running on a Windows Vista
- host. This is an installer issue. The workaround is to add
- an exception for port 3306 to the Windows Wista firewall
- manually.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Installing"/>
- </tags>
-
- <bugs>
- <fixes bugid="28628"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Config Wizard can't connect (race condition)
- </para>
-
- <itemizedlist>
-
- <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>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Installing"/>
- </tags>
-
- <bugs>
- <fixes bugid="28854"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: MySQL.prefPane does not start or stop mysql on osx 10.5
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Installing"/>
- </tags>
-
- <bugs>
<fixes bugid="31064"/>
</bugs>
@@ -3127,767 +134,6 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server: Installing"/>
- </tags>
-
- <bugs>
- <fixes bugid="31674"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: service doesn't start after upd 5.1.19 to 5.1.22
- because mysqld-nt.exe renamed
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: I_S"/>
- </tags>
-
- <bugs>
- <fixes bugid="25629"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>CREATE TABLE LIKE</literal> does not work with
- <literal>INFORMATION_SCHEMA</literal>
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: I_S"/>
- </tags>
-
- <bugs>
- <fixes bugid="30689"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Wrong content in
- <literal>I_S</literal>.<literal>VIEWS</literal>.<literal>VIEW_DEFINITION</literal>
- if <literal>VIEW</literal> is based on <literal>I_S</literal>
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- INFORMATION_SCHEMA.VIEWS.VIEW_DEFINITION was incorrect for
- views that are defined to select from other
- INFORMATION_SCHEMA tables.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Locking"/>
- </tags>
-
- <bugs>
- <fixes bugid="27440"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: read_only allows create and drop database
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Locking"/>
- </tags>
-
- <bugs>
- <fixes bugid="30294"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: blackhole engine causes 100% with 2 alter table
- statements running
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Locking"/>
- </tags>
-
- <bugs>
- <fixes bugid="32395"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Alter table under a impending global read lock causes a
- server crash
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Locking"/>
- </tags>
-
- <bugs>
- <fixes bugid="32676"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: insert delayed crash with wrong column and function
- specified ..
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Logging"/>
- </tags>
-
- <bugs>
- <fixes bugid="21557"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </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"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </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>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Merge"/>
- </tags>
-
- <bugs>
- <fixes bugid="25038"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Waiting <literal>TRUNCATE</literal>
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Merge"/>
- </tags>
-
- <bugs>
- <fixes bugid="25700"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: merge base tables get corrupted by
- optimize/analyze/repair table
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Merge"/>
- </tags>
-
- <bugs>
- <fixes bugid="26377"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Deadlock with <literal>MERGE</literal> and
- <literal>FLUSH TABLE</literal>
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- A deadlock can be created if use LOCK TABLES simultaneously
- on a MERGE and related MYISAM table and then run FLUSH
- TABLE, but only if specify the MERGE table before the
- corresponding MYISAM table in the LOCK TABLES statement.
- Specifying the MYISAM table before the MERGE table does not
- cause the same problem.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Merge"/>
- </tags>
-
- <bugs>
- <fixes bugid="26379"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Combination of <literal>FLUSH TABLE</literal> and
- <literal>REPAIR TABLE</literal> corrupts a
- <literal>MERGE</literal> table
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- A combination of factors is involved in this issue: (1) the
- table must be a MERGE table; (2) perform the statements LOCK
- TABLE, REPAIR TABLE, and FLUSH TABLE on the merge and base
- tables; (3) perform INSERTs from multiple threads into the
- merge table. A fix for this bug has been prepared and is
- expected to appear in 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Merge"/>
- </tags>
-
- <bugs>
- <fixes bugid="26867"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>LOCK TABLES</literal> +
- <literal>REPAIR</literal> + merge table result in memory/cpu
- hogging
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Using a MERGE table, issuing a REPAIR TABLE on one
- connection while a LOCK TABLES statement is in place and an
- INSERT statement on the same table is waiting on another
- connection causes signficant CPU/memory usage.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Merge"/>
- </tags>
-
- <bugs>
- <fixes bugid="30273"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: merge tables: Can't lock file (errno: 155)
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Merge"/>
- </tags>
-
- <bugs>
- <fixes bugid="30275"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Merge tables: flush tables or unlock tables causes
- server to crash
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- See description for Bug #26379.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: MyISAM"/>
- </tags>
-
- <bugs>
- <fixes bugid="28837"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: MyISAM storage engine error (134) doing delete with
- self-join
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: MyISAM"/>
- </tags>
-
- <bugs>
- <fixes bugid="29446"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Specifying a myisam_sort_buffer > 4GB on 64 bit
- machines not possible.
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- On 64-bit systems, specifying a myisam_sort_buffer size
- greater than 4GB would cause the value to wrap on the 4GB
- boundary. For example, a join_buffer of 5GB would actually
- only reserve 1GB. On 64-bit systems this restriction will be
- lifted. On 32-bit systems, the myisam_sort_buffer size will
- be limited to 4GB.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: MyISAM"/>
- </tags>
-
- <bugs>
- <fixes bugid="30284"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: spatial key corruption
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: MyISAM"/>
- </tags>
-
- <bugs>
- <fixes bugid="30286"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: spatial index cause corruption and server crash!
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Setting certain values on a table using a spatial index
- could cause the server to crash. The cause is the
- calculation of certain values which exceed the expected
- levels when converted to the format used by the spatial
- indexing, leading to the incorrect key being written to the
- database and subsequent index updates failing. There is no
- known work around.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: MyISAM"/>
- </tags>
-
- <bugs>
- <fixes bugid="30638"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: why doesn't > 4294967295 rows work in myisam on
- windows ?
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Inserting more than 2^32 (42924967295) rows into a single
- MYISAM table on windows, the row count is reset to 0. The
- data in the table is still accessible.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: MyISAM"/>
- </tags>
-
- <bugs>
- <fixes bugid="31158"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Spatial, Union, <literal>LONGBLOB</literal> vs
- <literal>BLOB</literal> bug (crops data)
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: MyISAM"/>
- </tags>
-
- <bugs>
- <fixes bugid="31305"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: myisam tables crash when they are near capacity
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server: NDBAPI"/>
</tags>
@@ -3919,1151 +165,10 @@
<logentry entrytype="custom" customname="open-bugs">
<tags>
- <manual type="Server: Optimizer"/>
- </tags>
-
- <bugs>
- <fixes bugid="31075"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: crash in get_func_mm_tree
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Queries that contained constructs of the form "WHERE col NOT
- IN (col, ...)" (where the same column is named both places)
- caused a range optimizer crash.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Optimizer"/>
- </tags>
-
- <bugs>
- <fixes bugid="32241"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: memory corruption due to large index map in 'Range
- checked for each record'
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Optimizer"/>
- </tags>
-
- <bugs>
- <fixes bugid="32400"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Complex <literal>SELECT</literal> query returns correct
- result only on some occasions
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Optimizer"/>
- </tags>
-
- <bugs>
- <fixes bugid="32403"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: query causes a crash due to stack and memory
- corruptions
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Optimizer"/>
- </tags>
-
- <bugs>
- <fixes bugid="32556"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: assert in "using index for group-by" : is_last_prefix
- <= 0, file .\opt_range.cc
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="29258"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Partitions: search fails for maximum unsigned bigint
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- If you create a table with PARTITION BY
- RANGE(unsigned_bigint_column) and PARTITION ... VALUES LESS
- THAN MAXVALUE, then try to insert the maximum possible value
- for BIGINT UNSIGNED (18446744073709551615), the INSERT
- statement apparently succeeds (in some cases with a warning,
- in others without one), but nothing is inserted into the
- table; the value is not truncated, and the statement does
- not produce an error.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="29444"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: crash with partition refering to table in create-select
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The fix for this issue has been committed; the server now
- checks to insure that an attempt to refer in a PARTITION BY
- clause to a column belonging to a different table from that
- referred to in the partition definitions is not allowed.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="30459"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.24"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Partitioning across disks failing on Windows Server
- (64-bit)
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="30583"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </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>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Apostrophe in <literal>PARTITION</literal> clause
- comment crashes the server
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- A patch has been committed for this issue and is expected to
- appear in 5.1.23 or 5.1.24.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="30822"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>ALTER TABLE COALESCE PARTITION</literal>
- causes segmentation fault
- </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: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="32178"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: server crash when select from i_s and concurrent
- partition management
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Performing partition management statements such as ALTER
- TABLE ... REORGANIZE PARTITION while performing SELECT
- queries from the INFORMATION_SCHEMA.PARTITIONS table causes
- mysqld to crash. 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: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="32247"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Test reports wrong value of
- "<literal>AUTO_INCREMENT</literal>" (on a partitioned InnoDB
- table)
- </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: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="32772"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: partition crash 1: enum column and double
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Queries involving ordered index scans could cause a server
- crash when a partitioned table has an ENUM, SET, or DOUBLE
- column, even if this column is not used as a partitioning
- key. A fix has been committed for this issue 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: Partition"/>
- </tags>
-
- <bugs>
- <fixes bugid="32948"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: FKs allowed to reference partitioned table
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Privileges"/>
- </tags>
-
- <bugs>
- <fixes bugid="30468"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: column level privileges not respected when joining
- tables
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- When expanding a * in a USING or NATURAL join, the check for
- table access for both tables in the join was done using the
- grant information of the first table
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: PS"/>
- </tags>
-
- <bugs>
- <fixes bugid="27430"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.25,6.0"/>
- <fixedin ver="5.1.25"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Crash in subquery code when in <literal>PS</literal>
- and table <literal>DDL</literal> changed after
- <literal>PREPARE</literal>
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Any user who is able to create/drop/alter tables may
- trivially crash the server daemon via the use of prepared
- statements. The only workaround to this possible DoS is to
- completely disallow prepared statements by setting the
- system variable max_prepared_stmt_count to 0.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Query Cache"/>
- </tags>
-
- <bugs>
- <fixes bugid="30768"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: query cache patch for bug #21074 crashes on windows
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The pthread_mutex_trylock() implementation is problematic on
- Windows and can cause a server crash when the query cache is
- invalidated. Workaround: Disable the query cache.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Query Cache"/>
- </tags>
-
- <bugs>
- <fixes bugid="30887"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Server crashes on <literal>SET GLOBAL</literal>
- query_cache_size=0
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="27779"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Slave cannot read old rows log events.
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- A slave running MySQL 5.1.19 or newer cannot read logs
- generated by a master running MySQL 5.1.18 or earlier. This
- issue was apparently introduced by the fix for Bug #22583 in
- MySQL 5.1.18. Work is in progress on a lasting solution for
- this issue.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="29020"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.24"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Event results not correctly replicated to slave in
- <literal>RBR</literal>
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- When an event has a short schedule (such as EVERY 1
- SECONDS), it can sometimes happen that the event executes on
- the master but its effects are not propagated to the slave.
- The fix for this issue depends on the fix for Bug #12713,
- which is expected in 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="29549"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Endians: rpl_ndb_myisam2ndb,rpl_ndb_innodb2ndb and
- rpl_ndb_mix_innodb failed on
- </para>
-
- <itemizedlist>
-
- <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>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="31552"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Replication breaks when deleting rows from out-of-sync
- table without <literal>PK</literal>
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="31609"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Not all <literal>RBR</literal> slave errors reported as
- errors
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- When using row based replication, the slave stops when
- attempting to delete non-existent rows from a slave table
- without a primary key. Known to occur with MyISAM, InnoDB
- and NDB tables. A fix for this issue has been committed, and
- is expected to appear in MySQL 5.1.23. See also Bug #31552
- and Bug #32468.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="32468"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: delete rows event on a table with foreign key
- constraint fails
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The deletion is successful on the master but fails on the
- slave. A fix for this issue is in progress. See also Bug
- #31552.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="33375"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: all_set corrupted on table object
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: RBR"/>
- </tags>
-
- <bugs>
- <fixes bugid="36197"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.25"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: flush tables (or little table cache) can cause crash on
- slave
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
<manual type="Server: Replication"/>
</tags>
<bugs>
- <fixes bugid="23333"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: stored function + non-transac table + transac table =
- breaks stmt-based binlog
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- An UPDATE statement setting a column of a non-transactional
- table to the value returned by a stored function that
- modifies is not logged if it fails, whereas any query that
- modifies a non-deterministic table should be logged even if
- there is an error in the execution. Otherwise, the master
- has a row in the non-transactional table that the slave does
- not have. A fix for this issue is pending; it is expected to
- appear in 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="26000"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>SHOW SLAVE STATUS</literal> can crash mysqld
- during shutdown process
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The sequence of events necessary to trigger this issue is
- unlikely to occur during normal manual operation, but may
- affect monitoring tools that execute SHOW SLAVE STATUS
- automatically. A fix has been done for this issue in 5.0 and
- is expected to be made to 5.1 in time for the 5.1-GA
- release.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="26199"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Replication of stored procedures with
- <literal>BIT</literal> parameters fails
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The workaround is to use parameters of INT types rather than
- BIT type.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="26395"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: if crash during autocommit update to transactional
- table on master, slave fails
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- When a statement modifies an innodb table in autocommit
- mode, and the master crashes afterwards, but before writing
- the corresponding log event to disk, then the binlog may
- contain only the INSERT. In such a case, when the master
- restarts, InnoDB will roll back. The slave replicates the
- INSERT but not the ROLLBACK, and so the result is that on
- master the statement has been rolled back while on slave it
- is executed. This does not occur with AUTOCOMMIT turned off,
- since explicit BEGIN, COMMIT, and ROLLBACK statements are
- generated and logged. A fix is in progress, but it is not
- known at this whether it will be ready to appear in 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
<fixes bugid="26980"/>
</bugs>
@@ -5089,771 +194,4 @@
</logentry>
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="28086"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>SBR</literal> of <literal>USER</literal>()
- becomes corrupted on slave
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Workaround: Use row-based rather than statement-based
- replication of USER().
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="28597"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Replication doesn't start after upgrading to 5.1.18
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- This issue was encountered when upgrading the master and
- slave from MySQL 5.1.16 to 5.1.18. A patch is pending and is
- expected to be included in MySQL 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="28618"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Skipping into the middle of a group with
- <literal>SQL_SLAVE_SKIP_COUNTER</literal> is possible
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- A fix for this issue has been committed and is expected to
- be included in MySQL 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="30752"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: rpl_dual_pos_advance valgrind (jump depends on
- 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>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="30790"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Suspicious code in rpl_utility.cc
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="30854"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Tables name show as binary in slave err msg on
- vm-win2003-64-b
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- This is probably a memory corruption issue. (The relevant
- error code is <errorcode>ER_BAD_FIELD_ERROR</errorcode>.)
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="30998"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Drop View breaks replication if view does not exist
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="31581"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: 5.1-telco-6.1 -> 5.1.22. Slave crashes during
- starting
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="31793"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: log event corruption causes crash
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="32205"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Replaying statements from mysqlbinlog fails with a
- syntax error, replicates fine
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="32407"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Impossible to do point-in-time recovery from older
- binlog
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
- <fixes bugid="32580"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysqlbinlog cannot read binlog event generated by user
- variable usage
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- This occurs when using statement-based or mixed binlogging
- mode. When a user variable (such as "@something") is used
- inside an INSERT statement, the statement is replicated with
- invalid SQL syntax. A fix for this issue has been committed,
- and should appear in MySQL 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: SP"/>
- </tags>
-
- <bugs>
- <fixes bugid="12713"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Error in a stored function called from a
- <literal>SELECT</literal> doesn't cause
- <literal>ROLLBACK</literal> of statem
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- When AUTOCOMMIT=1, an error in a stored function called from
- a SELECT statement fails to roll back the statement. This
- can have consequences for row-based replication, such as the
- problem with scheduled events encountered in Bug #29020. A
- fix for this issue is expected in 5.1.23.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: SP"/>
- </tags>
-
- <bugs>
- <fixes bugid="21801"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.24"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>SQL</literal> exception handlers and warnings
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: SP"/>
- </tags>
-
- <bugs>
- <fixes bugid="31898"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1.23"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: 16M memory allocations for user variables in stored
- procedure
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: SP"/>
- </tags>
-
- <bugs>
- <fixes bugid="33618"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.0+"/>
- <fixedin ver="5.1.24"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Crash in sp_rcontext
- </para>
-
- <itemizedlist>
-
- <listitem></listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Types"/>
- </tags>
-
- <bugs>
- <fixes bugid="30587"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: mysql crashes when trying to group by
- <literal>TIME</literal> div <literal>NUMBER</literal>
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Using GROUP BY on an expression of the form timestamp_col
- DIV number caused a server crash due to incorrect
- calculation of number of decimals.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Types"/>
- </tags>
-
- <bugs>
- <fixes bugid="30782"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Truncated <literal>UNSIGNED BIGINT</literal> columns
- only in <literal>SELECT</literal> w/ <literal>CASE</literal>,
- <literal>JOIN</literal>, and <literal>ORDER BY</literal>
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Types"/>
- </tags>
-
- <bugs>
- <fixes bugid="30955"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %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>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Types"/>
- </tags>
-
- <bugs>
- <fixes bugid="32180"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>DATE_ADD</literal> treats datetime numeric
- argument as <literal>DATE</literal> instead of
- <literal>DATETIME</literal>
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Types"/>
- </tags>
-
- <bugs>
- <fixes bugid="32198"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Comparison of <literal>DATE</literal> with
- <literal>DATETIME</literal> still not using indexes correctly
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Types"/>
- </tags>
-
- <bugs>
- <fixes bugid="32282"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: <literal>TEXT</literal> silently truncates when value
- is exactly 65536 bytes
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Types"/>
- </tags>
-
- <bugs>
- <fixes bugid="32848"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <fixedin ver="5.1.23"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Data type conversion bug in union subselects in MySQL
- 5.0.38
- </para>
-
- </message>
-
- </logentry>
-
</changelog>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11266 - trunk/dynamic-docs/open-bugs | mcbrown | 16 Jul |
