FW: MySQL Community Server 5.0.82 has been released
- From: "Sina Bahram" <sbahram@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Thu, 28 May 2009 01:03:54 -0400
For you MySQL users out there.
See below
Take care,
Sina
-----Original Message-----
From: Karen.Langford@xxxxxxx [mailto:Karen.Langford@xxxxxxx]
Sent: Wednesday, May 27, 2009 7:43 PM
To: announce@xxxxxxxxxxxxxxx
Cc: mysql@xxxxxxxxxxxxxxx; packagers@xxxxxxxxxxxxxxx
Subject: MySQL Community Server 5.0.82 has been released
Dear MySQL users,
MySQL Community Server 5.0.82, a new version of the popular Open Source
Database Management System, has been released. This and future releases
in the MySQL Community Server 5.0 series share version numbers with
their MySQL Enterprise Server counterparts.
The release is now available in source and binary form for a number of
platforms from our download pages at
http://dev.mysql.com/downloads/
and mirror sites. Note that 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
Please note that we have dropped support for AIX 5.2 as of April 30th
as the platform has reached vendor EOL, and this is the first release
of MySQL 5.0 which does not include binaries for that platform.
http://dev.mysql.com/doc/refman/5.0/en/releasenotes-cs-5-0-82.html
This section documents all changes and bugfixes that have been
applied since the last MySQL Community Server release (5.0.81).
If you would like to receive more fine-grained and personalized
update alerts about fixes that are relevant to the version and
features you use, please consider subscribing to MySQL Enterprise
(a commercial MySQL offering). For more details please see
http://www.mysql.com/products/enterprise/advisors.html.
* Replication: Restarting the replication slave --- either by
using STOP SLAVE plus START SLAVE, or by restarting the slave
mysqld process --- could sometimes cause the slave to crash
when using a debug version of the server.
(Bug#38694: http://bugs.mysql.com/38694)
* Replication: Killing the thread executing a DDL statement,
after it had finished its execution but before it had written
the binlog event, caused the error code in the binlog event to
be set (incorrectly) to ER_SERVER_SHUTDOWN or
ER_QUERY_INTERRUPTED, which caused replication to fail.
(Bug#37145: http://bugs.mysql.com/37145)
See also Bug#27571: http://bugs.mysql.com/27571,
Bug#22725: http://bugs.mysql.com/22725.
* Replication: Column aliases used inside subqueries were ignored
in the binary log. (Bug#35515: http://bugs.mysql.com/35515)
* Replication: The statements DROP PROCEDURE IF EXISTS and DROP
FUNCTION IF EXISTS were not written to the binary log if the
procedure or function to be dropped did not exist.
(Bug#13684: http://bugs.mysql.com/13684)
See also Bug#25705: http://bugs.mysql.com/25705.
* Use of HANDLER statements with INFORMATION_SCHEMA tables
caused a server crash. Now HANDLER is prohibited with such
tables. (Bug#44151: http://bugs.mysql.com/44151)
* myisamchk could display a negative Max keyfile length value.
(Bug#43950: http://bugs.mysql.com/43950)
* On Windows, a server crash occurred for attempts to insert a
floating-point value into a CHAR column with a maximum length
less than the converted floating-point value length.
(Bug#43833: http://bugs.mysql.com/43833)
* UNION of floating-point numbers did unnecessary rounding.
(Bug#43432: http://bugs.mysql.com/43432)
* Certain statements might open a table and then wait for an
impending global read lock without noticing whether they hold
a table being waiting for by the global read lock, causing a
hang. Affected statements are SELECT ... FOR UPDATE, LOCK
TABLES ... WRITE, TRUNCATE TABLE, and LOAD DATA INFILE.
(Bug#43230: http://bugs.mysql.com/43230)
* The InnoDB btr_search_drop_page_hash_when_freed() function had
a race condition. (Bug#42279: http://bugs.mysql.com/42279)
* Compressing a table with the myisampack utility caused the
server to produce Valgrind warnings when it opened the table.
(Bug#41541: http://bugs.mysql.com/41541)
* For a MyISAM table with DELAY_KEY_WRITE enabled, the index
file could be corrupted without the table being marked as
crashed if the server was killed.
(Bug#41330: http://bugs.mysql.com/41330)
* Multiple-table UPDATE statements did not properly activate
triggers. (Bug#39953: http://bugs.mysql.com/39953)
* An UPDATE statement that updated a column using the same
DES_ENCRYPT() value for each row actually updated different
rows with different values.
(Bug#35087: http://bugs.mysql.com/35087)
* For shared-memory connections, the read and write methods did
not properly handle asynchronous close events, which could
lead to the client locking up waiting for a server response.
For example, a call to mysql_real_query() would block forever
on the client side if the executed statement was aborted on
the server side. Thanks to Armin Schöffmann for the bug report
and patch. (Bug#33899: http://bugs.mysql.com/33899)
* CHECKSUM TABLE was not killable with KILL QUERY.
(Bug#33146: http://bugs.mysql.com/33146)
* myisamchk and myisampack were not being linked with the
library that enabled support for * filename pattern expansion.
(Bug#29248: http://bugs.mysql.com/29248)
* COMMIT did not delete savepoints if there were no changes in
the transaction. (Bug#26288: http://bugs.mysql.com/26288)
* Several memory allocation functions were not being checked for
out-of-memory return values.
(Bug#25058: http://bugs.mysql.com/25058)
Thanks,
Karen
Karen Langford, MySQL Release Engineer
Database Group, Sun Microsystem Inc.
--
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
To unsubscribe: http://lists.mysql.com/announce?unsub=sbahram@xxxxxxxxx
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
- » FW: MySQL Community Server 5.0.82 has been released - Sina Bahram
