List:Announcements« Previous MessageNext Message »
From:Murthy Narkedimilli Date:June 6 2013 2:31pm
Subject:MySQL Community Server 5.1.70 has been released
View as plain text  
Dear MySQL users,

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

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/relnotes/mysql/5.1/en/news-5-1-70.html

Enjoy!


Changes in MySQL 5.1.70 (Not yet released)

    Bugs Fixed

      * Important Change; Replication: When the server was running
        with --binlog-ignore-db and SELECT DATABASE() returned NULL
        (that is, there was no currently selected database),
        statements using fully qualified table names in dbname.tblname
        format were not written to the binary log. This was because
        the lack of a currently selected database in such cases was
        treated as a match for any possible ignore option rather than
        for no such option; this meant that these statements were
        always ignored.
        Now, if there is no current database, a statement using fully
        qualified table names is always written to the binary log.
        (Bug #11829838, Bug #60188)

      * InnoDB: Valgrind testing returned memory leak errors which
        resulted from a regression introduced by the fix for Bug
        #11753153. The dict_create_add_foreign_to_dictionary function
        would call pars_info_create but failed to call pars_info_free.
        (Bug #16754901)

      * InnoDB: The fix for Bug #16722314 resulted in a linker error.
        (Bug #16798595)

      * InnoDB: Crash recovery would fail with a !recv_no_log_write
        assertion when reading a page. (Bug #16405422)

      * Replication: Using the --replicate-* options (see Replication
        Slave Options and Variables
(http://dev.mysql.com/doc/refman/5.1/en/replication-options-sl
        ave.html)) could in some cases lead to a memory leak on the
        slave. (Bug #16056813, Bug #67983)

      * The WKB reader for spatial operations could fail and cause a
        server exit. (Bug #16451878)

      * A GROUP_CONCAT() invocation containing subquery having an
        outer reference caused the server to exit. (Bug #16347343)

      * For debug builds, GROUP_CONCAT(... ORDER BY) within an ORDER
        BY clause could cause a server exit. (Bug #16347426)

      * A prepared statement that used GROUP_CONCAT() and an ORDER BY
        clause that named multiple columns could cause the server to
        exit. (Bug #16075310)

      * ORDER BY MATCH ... AGAINST could cause a server exit. (Bug
        #16073689)

      * When a partition is missing, code in ha_innodb.cc would retry
        10 times and sleep for a microsecond each time while holding
        LOCK_open. The retry logic for partitioned tables was
        introduced as a fix for Bug#33349 but did not include a test
        case to validate it. This fix removes the retry logic for
        partitioned tables. If the problem reported in Bug#33349
        reappears, a different solution will be explored. (Bug
        #15973904)

      * The mysql.server script exited with an error if the status
        command was executed with multiple servers running. (Bug
        #15852074)

      * When processing row-based-replication events in the old binary
        log format from prior to MySQL 5.1 GA builds, mysqlbinlog
        could result in out-of-bounds heap buffer reads and undefined
        behaviour. (Bug #14771299)

      * The mysql client allocated but did not free a string after
        reading each line in interactive mode, resulting in a memory
        leak. (Bug #14685362)

      * Grouping by an outer BLOB column in a subquery caused a server
        exit. (Bug #13966809, Bug #14700180)

      * The url columns in the mysql datatbase help tables were too
        short to hold some of the URLs in the help content. For new
        installations, these columns are now created as type TEXT to
        accommodate longer URLs.
        For upgrades, mysql_upgrade does not update the columns.
        Modify them manually using these statements:
ALTER TABLE mysql.help_category MODIFY url TEXT NOT NULL;
ALTER TABLE mysql.help_topic MODIFY url TEXT NOT NULL;
        (Bug #61520, Bug #12671635)

      * The test for stack overrun did not work for recent gcc
        versions and could lead to server exit. (Bug #62856, Bug
        #13243248)
        References: See also Bug #42213.

      * IF() function evaluations could produce different results when
        executed in a prepared versus nonprepared statement. (Bug
        #45370, Bug #11753852)

On behalf of Oracle MySQL RE Team

Murthy Narkedimilli





Thread
MySQL Community Server 5.1.70 has been releasedMurthy Narkedimilli9 Jun