MySQL Community Server 5.1.61 has been released

[hery ramilison]

Dear MySQL users,

MySQL Server 5.1.61, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.61 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.61 on new servers or upgrading
to MySQL 5.1.61 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/open-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-61.html

Enjoy!

=======================================================================
D.1.1. Changes in MySQL 5.1.61 (10 January, 2012)


   Bugs Fixed

     * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY
       statements for InnoDB tables from concurrent threads could
       cause a deadlock
       (http://dev.mysql.com/doc/refman/5.5/en/glossary.html#glos_dea
       dlock), particularly with the INSERT...ON DUPLICATE KEY UPDATE
       form. The fix avoids deadlocks caused by the same row being
       accessed by more than one transaction. Deadlocks could still
       occur when multiple rows are inserted and updated
       simultaneously by different transactions in inconsistent
       order; those types of deadlocks require the standard error
       handling on the application side, of re-trying the
       transaction. (Bug #11759688, Bug #52020)

     * An incorrect InnoDB assertion could cause the server to halt.
       This issue only affected debug builds. The assertion
       referenced the source file btr0pcur.ic and the variable
       cursor->pos_state. (Bug #13358468)

     * The handle_segfault() signal-handler code in mysqld could
       itself crash due to calling unsafe functions. (Bug #54082, Bug
       #11761576)

     * ARCHIVE tables with NULL columns could cause server crashes or
       become corrupt under concurrent load. (Bug #51252, Bug
       #11758979)

     * Enabling myisam_use_mmap could cause the server to crash. (Bug
       #48726, Bug #11756764)

     * Concurrent access to ARCHIVE tables could cause corruption.
       (Bug #42784, Bug #11751793)


Thanks,
MySQL RE Team
Database Group, Oracle.