List:Announcements« Previous MessageNext Message »
From:Sunanda Menon Date:May 7 2012 11:09am
Subject:MySQL Community Server 5.1.63 has been released
View as plain text  
Dear MySQL users,

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

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

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

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

http://dev.mysql.com/doc/refman/5.1/en/installing.html

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

http://dev.mysql.com/downloads/

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.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/bugs.html

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

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html

Enjoy!

=======================================================================
D.1.1. Changes in MySQL 5.1.63 (7th May, 2012)

    Bugs Fixed

      * Security Fix: Bug #64884 was fixed.

      * Security Fix: Bug #59387 was fixed.

      * InnoDB: Deleting a huge amount of data from InnoDB tables
        within a short time could cause the purge operation that
        flushes data from the buffer pool to stall. If this issue
        occurs, restart the server to work around it. This issue is
        only likely to occur on 32-bit platforms. (Bug #13847885)

      * InnoDB: If the server crashed during a TRUNCATE TABLE or
        CREATE INDEX statement for an InnoDB table, or a DROP DATABASE
        statement for a database containing InnoDB tables, an index
        could be corrupted, causing an error message when accessing
        the table after restart:
        InnoDB: Error: trying to load index index_name for table
        table_name
        InnoDB: but the index tree has been freed!
        In MySQL 5.1, this fix applies to the InnoDB Plugin, but not
        the built-in InnoDB storage engine. (Bug #12861864, Bug
        #11766019)

      * InnoDB: When data was removed from an InnoDB table, newly
        inserted data might not reuse the freed disk blocks, leading
        to an unexpected size increase for the system tablespace or
        .ibd file (depending on the setting of innodb_file_per_table.
        The OPTIMIZE TABLE could compact a .ibd file in some cases but
        not others. The freed disk blocks would eventually be reused
        as additional data was inserted. (Bug #11766634, Bug #59783)

      * Partitioning: After updating a row of a partitioned table and
        selecting that row within the same transaction with the query
        cache enabled, then performing a ROLLBACK, the same result was
        returned by an identical SELECT issued in a new transaction.
        (Bug #11761296, Bug #53775)

      * Replication: The --relay-log-space-limit option was sometimes
        ignored.
        More specifically, when the SQL thread went to sleep, it
        allowed the I/O thread to queue additional events in such a
        way that the relay log space limit was bypassed, and the
        number of events in the queue could grow well past the point
        where the relay logs needed to be rotated. Now in such cases,
        the SQL thread checks to see whether the I/O thread should
        rotate and provide the SQL thread a chance to purge the logs
        (thus freeing space).
        Note that, when the SQL thread is in the middle of a
        transaction, it cannot purge the logs; it can only ask for
        more events until the transaction is complete. Once the
        transaction is finished, the SQL thread can immediately
        instruct the I/O thread to rotate. (Bug #12400313, Bug #64503)
        References: See also Bug #13806492.

      * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored
        procedures on slave servers could cause replication failures.
        (Bug #12601974)

      * If the system time was adjusted backward during query
        execution, the apparent execution time could be negative. But
        in some cases these queries would be written to the slow query
        log, with the negative execution time written as a large
        unsigned number. Now statements with apparent negative
        execution time are not written to the slow query log. (Bug
        #63524, Bug #13454045) References: See also Bug #27208.

      * mysql_store_result() and mysql_use_result() are not for use
        with prepared statements and are not intended to be called
        following mysql_stmt_execute(), but failed to return an error
        when invoked that way in libmysqld. (Bug #62136, Bug
        #13738989) References: See also Bug #47485.

      * SHOW statements treated stored procedure, stored function, and
        event names as case sensitive. (Bug #56224, Bug #11763507)

      * On Windows, mysqlslap crashed for attempts to connect using
        shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug
        #11766072)

Thanks,
On Behalf of, Oracle MySQL RE Team

Sunanda Menon
MySQL Release Engineer






Thread
MySQL Community Server 5.1.63 has been releasedSunanda Menon7 May