Dear MySQL users,
MySQL Server 5.5.35 is a new version of the 5.5 production release
of the world's most popular open source database. MySQL 5.5.35 is
recommended for use on production systems.
MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL Database, taking advantage of
the latest multi-CPU and multi-core hardware and operating systems. In
addition, with release 5.5, InnoDB is now the default storage engine for
the MySQL Database, delivering ACID transactions, referential integrity
and crash recovery by default.
MySQL 5.5 also provides a number of additional enhancements including:
- Significantly improved performance on Windows, with various
Windows specific features and improvements
- Higher availability, with new semi-synchronous replication and
Replication Heartbeat
- Improved usability, with Improved index and table partitioning,
SIGNAL/RESIGNAL support and enhanced diagnostics, including a new
Performance Schema monitoring capability.
For a more complete look at what's new in MySQL 5.5, please see the
following resources:
MySQL 5.5 is GA, Interview with Tomas Ulin:
http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html
Documentation:
http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html
Whitepaper: What's New in MySQL 5.5:
http://www.mysql.com/why-mysql/white-papers/whats-new-in-mysql-5-5/
If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.
http://mysql.com/products/enterprise/
For information on installing MySQL 5.5.35 on new servers, please see
the MySQL installation documentation at
http://dev.mysql.com/doc/refman/5.5/en/installing.html
For upgrading from previous MySQL releases, please see the important
upgrade considerations at:
http://dev.mysql.com/doc/refman/5.5/en/upgrading.html
MySQL Database 5.5.35 is available in source and binary form for a
number of platforms from our download pages at:
http://dev.mysql.com/downloads/mysql/
The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.5. It may also be viewed
online at:
http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-35.html
Enjoy!
Changes in MySQL 5.5.35 (2013-12-03)
Functionality Added or Changed
* A new CMake option, WITH_ASAN, permits enabling address
sanitization for compilers that support it. (Bug #17435338)
* Attempts to use the thread_concurrency system variable (which
has an effect only for Solaris 8 and earlier) now indicate
that it has no effect when that is the case. (Bug #67944, Bug
#16032946)
Bugs Fixed
* InnoDB: Running SHOW ENGINE INNODB STATUS on one connection
thread and killing that thread by running a KILL CONNECTION
statement from a different connection thread would result in a
severe error. (Bug #17474166)
* InnoDB: CHECK TABLE would ignore the QUICK option. (Bug
#17513737)
* InnoDB: In debug builds, test case failures would occur due to
ibuf_contract_ext performing merges and dict_stats_update
returning evicted pages back into the buffer pool while
ibuf_change_buffering_debug is enabled. (Bug #17446090)
* InnoDB: InnoDB would fail to return an error when attempting
to run a query after discarding the tablespace. (Bug
#17431533)
* InnoDB: When the change buffer is enabled, InnoDB would fail
to write a transaction log record when merging a record from
the insert buffer to a secondary index page if the insert was
performed as an "update-in-place". (Bug #16752251, Bug #69122)
* InnoDB: When index_read_map is called for an exact search and
fails to return a record due to non-matching search criteria,
the cursor would be positioned on the next record after the
searched key. A subsequent call to index_next would return the
next record instead of returning the previous non-matching
row, thereby skipping a record. (Bug #14621190, Bug #15965874)
* InnoDB: Converting a table with a large number of columns from
MyISAM to InnoDB would cause an assertion due to insufficient
log buffer space. Instead of asserting, InnoDB now attempts to
increase log buffer size automatically if the redo log size is
too large. (Bug #11758196, Bug #50366)
* Partitioning: After disabling the parent table's indexes with
ALTER TABLE ... DISABLE KEYS, rebuilding any of its partitions
enabled the indexes on those partitions, leading MyISAM to
fail with an error when the optimizer tried to use one of the
affected indexes.
Now in such cases, we check for disabled indexes on the table
before rebuilding any of its partitions. If the indexes have
been disabled, then we disable them on the partition following
the rebuild. (Bug #16051817)
* Replication: A replication master did not handle correctly the
disabling of the semisync plugin on the master and the slave,
with a subsequent stopping of the slave. (Bug #17460821, Bug
#70349)
* Replication: The final argument in the SET clause of a LOAD
DATA ... SET statement was repeated in the binary log. (Bug
#17429677, Bug #70277)
* Replication: When an error encountered by the dump thread
while reading events from the active binary log file was a
temporary error, so that the dump thread tried to read the
event, it was possible for the dump thread to seek the wrong
position, which could cause one or more events to be resent.
To prevent this, the thread's position is obtained after each
correct read of an event.
In addition, with this fix, only binary logs that are not
closed normally are marked as possibly being corrupted.
Finally, two warnings are added; these are now returned when a
dump thread encounters a temporary error. (Bug #17402313)
* Replication: Setting rpl_semi_sync_master_enabled while the
master was waiting for a reply from the slave could in some
cases cause the master to fail. (Bug #17327454, Bug #70045)
* Replication: The value of LAST_INSERT_ID() was not correctly
replicated when filtering rules were used on the slave. (Bug
#17234370, Bug #69861)
* The mysql_options() C API function could leak memory if called
more than once with the MYSQL_SET_CLIENT_IP option. (Bug
#17297012)
* The CONV() function could call abs(INT_MIN), which is
undefined, and cause a server exit. (Bug #17296644)
* An error array in the SSL code was missing a comma, leading to
implicit concatenation of adjacent messages and a resulting
off-by-one error in the relationship between error numbers and
messages. (Bug #17294150)
* GROUP_CONCAT() with an invalid separator could cause a server
exit. (Bug #16870783)
* An internal InnoDB string routine could write past the end of
a buffer. (Bug #16765410)
* Using the binary client/server protocol, the second execution
of a prepared statement for a query with parameters in the
LIMIT clause raised an assertion. (Bug #16346241)
* Very long database names in queries could cause the server to
exit. (Bug #15912213, Bug #16900358)
* The my_b_vprintf() function could produce incorrect results
for long integers on 64-bit systems. (Bug #67386, Bug
#16978278)
* COUNT(DISTINCT) should not count NULL values, but they were
counted when the optimizer used Loose Index Scan. (Bug #69841,
Bug #17222452)
* For queries of the form UPDATE ... WHERE unique_key ORDER BY
... LIMIT ..., incorrect rows could be updated. Unique keys
permit multiple NULL values, but the optimizer did not always
consider all of them. (Bug #68656, Bug #16482467)
* Killing a query that is performing a filesort operation
resulted in an ER_SERVER_SHUTDOWN (Server shutdown in progess)
error. (Bug #18256, Bug #11745656)
On Behalf of Oracle/MySQL RE Team,
Laasya Moduludu
↧
MySQL Community Server 5.5.35 has been released (no replies)
↧