Dear MySQL users,
MySQL 5.5.17 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.17 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 Heart Beat
- 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://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php
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.17 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.17 is available in source and binary form for a
number of platforms from our download pages at:
http://dev.mysql.com/downloads/mysql/
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
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/refman/5.5/en/news-5-5-17.html
Enjoy!
Platform note:
* Starting with MySQL 5.5.17, RPM packages for Enterprise Linux 6
(available from Oracle) are being built and published.
In all conventions (naming, dependencies, build options),
they do not differ from the RPM packages for SuSE and RedHat
distributions, but they are built natively on Enterprise Linux.
D.1.2. Changes in MySQL 5.5.17 (19 October 2011)
Functionality Added or Changed
* Replication: Previously, replication slaves could connect to
the master server only through master accounts that use native
authentication. Now replication slaves can also connect
through master accounts that use nonnative authentication
(except Windows native authentication) if the required
client-side plugin is installed on the slave side in the
directory named by the slave plugin_dir system variable. (Bug
#12897501)
* MEMORY table creation time is now available in the CREATE_TIME
column of the INFORMATION_SCHEMA.TABLES table and the
Create_time column of SHOW TABLE STATUS output. (Bug #51655,
Bug #11759349)
Bugs Fixed
* InnoDB Storage Engine: This fix improves the performance of
instrumentation code for InnoDB buffer pool operations. (Bug
#12950803, Bug #62294)
* InnoDB Storage Engine: Data from BLOB columns could be lost if
the server crashed at a precise moment when other columns were
being updated in an InnoDB table. (Bug #12704861)
* InnoDB Storage Engine: Lookups using secondary indexes could
give incorrect matches under a specific set of conditions. The
conditions involve an index defined on a column prefix, for a
BLOB or other long column stored outside the index page, with
a table using the Barracuda file format. (Bug #12601439)
* InnoDB Storage Engine: This fix corrects cases where the MySQL
server could hang or abort with a long semaphore wait message.
(This is a different issue than when these symptoms occurred
during a CHECK TABLE statement.) (Bug #11766591, Bug #59733)
* Internal
