MySQL Forums
Forum List  »  Announcements

MySQL Community Server 5.1.69 has been released
Posted by: Akhil Mohan
Date: April 18, 2013 07:07AM

Dear MySQL users,

MySQL Server 5.1.69, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.69 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

For information on installing MySQL 5.1.69 on new servers or upgrading
to MySQL 5.1.68 from previous MySQL releases, please see

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at


Changes in MySQL 5.1.69 (18-04-2013)
   Functionality Added or Changed

     * MySQL no longer uses the default OpenSSL compression. (Bug

   Bugs Fixed

     * InnoDB; Performance: The DROP TABLE statement for a table
       using compression
       pression) could be slower than necessary, causing a stall for
       several seconds. MySQL was unnecessarily decompressing pages
       e) in the buffer pool
       fer_pool) related to the table as part of the DROP operation.
       (Bug #16067973)

     * Important Note; Replication: It was possible to replicate from
       a table to a same-named view using statement-based logging,
       while using row-based logging instead led to a failure on the
       slave. Now the target object type is checked prior to
       performing any DML, and an error is given if the target on the
       slave is not actually a table. This is true regardless of the
       binary logging format in use. (Bug #11752707, Bug #43975)

     * InnoDB: This fix makes MySQL more responsive to KILL QUERY
       statements when the query is accessing an InnoDB table. (Bug

     * InnoDB: When printing out long semaphore wait diagnostics,
       sync_array_cell_print() ran into a segmentation violation
       (SEGV) caused by a race condition. This fix addresses the race
       condition by allowing the cell to be freed while it is being
       printed. (Bug #13997024)

     * InnoDB: Killing a query caused an InnoDB assertion failure
       when the same table (cursor) instance was used again. This is
       the result of a regression error introduced by the fix for
       Bug#14704286. The fix introduced a check to handle kill
       signals for long running queries but the cursor was not
       restored to the proper state. (Bug #68051, Bug #16088883)

     * InnoDB: The length of internally generated foreign key names
       was not checked. If internally generated foreign key names
       were over the 64 character limit, this resulted in invalid DDL
       from SHOW CREATE TABLE. This fix checks the length of
       internally generated foreign key names and reports an error
       message if the limit is exceeded. (Bug #44541, Bug #11753153)

     * Partitioning: A query on a table partitioned by range and
       using TO_DAYS() as a partitioing function always included the
       first partition of the table when pruning. This happened
       regardless of the range employed in the BETWEEN clause of such
       a query. (Bug #15843818, Bug #49754)

     * Replication: A zero-length name for a user variable (such as
       @``) was incorrectly considered to be a sign of data or
       network corruption when reading from the binary log. (Bug
       #16200555, Bug #68135)

     * Replication: Backtick (`) characters were not always handled
       correctly in internally generated SQL statements, which could
       sometimes lead to errors on the slave. (Bug #16084594, Bug
       References: This bug is a regression of Bug #14548159, Bug

     * A long database name in a GRANT statement could cause the
       server to exit. (Bug #16372927)

     * Incorrect results were returned if a query contained a
       subquery in an IN clause which contained an XOR operation in
       the WHERE clause. (Bug #16311231)

     * Invocation of the range optimizer for a NULL select caused the
       server to exit. (Bug #16192219)

     * yaSSL did not perform proper padding checks, but instead
       examined only the last byte of plaintext and used it to
       determine how many bytes to remove. (Bug #16218104)

     * SHOW COLUMNS on a view defined as a UNION of Geometry columns
       could cause the server to exit. (Bug #14362617)

     * A LIKE pattern with too many '%' wildcards could cause a
       segmentation fault. (Bug #14303860)

     * SET var_name = VALUES(col_name) could cause the server to
       exit. This syntax is now prohibited because in SET context
       there is no column name and the statement returns
       ER_BAD_FIELD_ERROR. (Bug #14211565)

     * The COM_CHANGE_USER command in the client/server protocol did
       not properly use the character set number in the command
       packet, leading to incorrect character set conversion of other
       values in the packet. (Bug #14163155)

     * Subqueries with OUTER JOIN could return incorrect results if
       the subquery referred to a column from another SELECT. (Bug

     * Field_geom::reset() failed to reset its base Field_blob. The
       range optimizer used the uninitialized field during
       optimization and execution, causing the server to exit. (Bug

     * mysql_install_db did not escape '_' in the host name for
       statements written to the grant tables. (Bug #11746817)

     * PARTITION BY KEY on a utf32 ENUM column raised a debugging
       assertion. (Bug #52121, Bug #11759782)

     * The optimizer used loose index scan for some queries for which
       this access method is inapplicable. (Bug #42785, Bug

     * If a dump file contained a view with one character set and
       collation defined on a view with a different character set and
       collation, attempts to restore the dump file failed with an
       "illegal mix of collations" error. (Bug #65382, Bug #14117025)

     * The REPLACE() function produced incorrect results when a user
       variable was supplied as an argument and the operation was
       performed on multiple rows. (Bug #49271, Bug #11757250)

     * UNION ALL on BLOB columns could produce incorrect results.
       (Bug #50136, Bug #11758009)

     * View access in low memory conditions could raise a debugging
       assertion. (Bug #39307, Bug #11749556)

     * Setting max_connections to a value less than the current
       number of open connections caused the server to exit. (Bug
       #44100, Bug #11752803)

     * Incorrect metadata could be produced for columns returned from
       some views. (Bug #65379, Bug #14096619)

     * For debug builds, some queries with SELECT ... FROM DUAL
       nested subqueries raised an assertion. (Bug #60305, Bug

     * Adjusted MySQL configuration to account for change in Automake
       1.12 that produced sql_yacc.hh rather than sql_yacc.h as
       expected by sql/ (Bug #67177, Bug #15967374)
On behalf of Oracle MySQL RE Team

Akhil Mohan
MySQL Release Engineer

Options: ReplyQuote

Written By
MySQL Community Server 5.1.69 has been released
April 18, 2013 07:07AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.