MySQL Database Server 5.1.58 has been released

Dear MySQL users,

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

Enjoy!

============================================================ ===========
Changes in MySQL 5.1.58 (July 5th, 2011)

Bugs fixed:

* InnoDB Storage Engine: If the server crashed while an XA
transaction was prepared but not yet committed, the
transaction could remain in the system after restart, and
cause a subsequent shutdown to hang. (Bug #11766513, Bug
#59641)

* Partitioning: When executing a row-ordered retrieval index
merge, the partitioning handler used memory from that
allocated for the table, rather than allocated to the
query, causing table object memory not to be freed until the
table was closed. (Bug #11766249, Bug #59316)

* Replication: When mysqlbinlog was invoked using
--base64-output=decode-row and --start-position=pos, (where
pos is a point in the binary log past the format description
log event), a spurious error of the type shown here was
generated:

malformed binlog: it does not contain any Format_description_log_event...

However, since there is nothing unsafe about not printing the
format description log event, the error has been removed for
this case. (Bug #12354268)

* Replication: Typographical errors appeared in the text of
several replication error messages. (The word "position" was
misspelled as "postion".) (Bug #11762616, Bug #55229)

* After the fix for Bug#11889186, MAKEDATE() arguments with a
year part greater than 9999 raised an assertion. (Bug
#12403504)

* An assertion could be raised due to a missing NULL value check
in Item_func_round::fix_length_and_dec(). (Bug #12392636)

* In debug builds on Solaris, an assertion was raised if a
reverse IP lookup with gethostbyaddr_r() failed. (Bug
#12377872)

* MySQL did not build if configured with both --with-debug and
--with-libedit. (Bug #12329909)

* A problem introduced in 5.1.57 caused very old (MySQL 4.0)
clients to be unable to connect to the server. (Bug #61222,
Bug #12563279)

* Using CREATE EVENT IF NOT EXISTS for an event that already
existed and was enabled caused multiple instances of the event
to run. (Bug #61005, Bug #12546938)

* The incorrect max_length value for YEAR values could be used
in temporary result tables for UNION, leading to incorrect
results. (Bug #59343, Bug #11766270)

* In Item_func_in::fix_length_and_dec(), a Valgrind warning for
uninitialized values was corrected. (Bug #59270, Bug
#11766212)

* In ROUND() calculations, a Valgrind warning for uninitialized
memory was corrected. (Bug #58937, Bug #11765923)

* Valgrind warnings caused by comparing index values to an
uninitialized field were corrected. (Bug #58705, Bug
#11765713)

* LOAD DATA INFILE errors could leak I/O cache memory. (Bug
#58072, Bug #11765141)

* For LOAD DATA INFILE, multibyte character sequences could be
pushed onto a stack too small to accommodate them. (Bug
#58069, Bug #11765139)

* An embedded client would abort rather than issue an error
message if it issued a TEE command (\T file_name) and the
directory containing the file did not exist. This occurred
because the wrong error handler was called. (Bug #57491, Bug
#11764633)

* In debug builds, Field_new_decimal::store_value() was subject
to buffer overflows. (Bug #55436, Bug #11762799)

* On Linux, the mysql client built using the bundled libedit did
not read ~/.editrc. (Bug #49967, Bug #11757855)

* The optimizer sometimes incorrectly processed HAVING clauses
for queries that did not also have an ORDER BY clause. (Bug
#48916, Bug #11756928)

* PROCEDURE ANALYZE() could leak memory for NULL results, and
could return incorrect results if used with a LIMIT clause.
(Bug #48137, Bug #11756242)

* On some platforms, the Incorrect value: xxx for column yyy at
row zzz error produced by LOAD DATA INFILE could have an
incorrect value of zzz. (Bug #46895, Bug #11755168)

* In MySQL 5.1 and up, if a table had triggers that used syntax
supported in 5.0 but not 5.1, the table became unavailable.
Now the table is marked as having broken triggers. (Bug
#45235, Bug #11753738)

* An attempt to install nonexistent files during installation
was corrected. (Bug #43247, Bug #11752142)

* On FreeBSD 64-built builds of the embedded server, exceptions
were not prevented from propagating into the embedded
application. (Bug #38965, Bug #11749418)

Thanks,
MySQL RE Team
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org