Dear MySQL users,
MySQL Server 5.5.57 is a new version of the 5.5 production release
of the world's most popular open source database. MySQL 5.5.57 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:
Documentation:
http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html
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.57 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.57 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 link lists the changes in the MySQL 5.5 since
the release of MySQL 5.5.56 It may also be viewed online at:
http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-57.html
Enjoy!
Changes in MySQL 5.5.57 (2017-07-17)
* Packaging Notes
* Functionality Added or Changed
* Bugs Fixed
Packaging Notes
* mysqladmin was added to Docker/Minimal packages because
it is needed by InnoDB Cluster. (Bug #25998285)
Functionality Added or Changed
* The mysql client now supports a --binary-as-hex option
that causes display of binary data using hexadecimal
notation (0xvalue). Thanks to Daniël van Eeden for the
patch. (Bug #25340722, Bug #84391)
Bugs Fixed
* Replication: If a relay log index file named relay log
files that did not exist, RESET SLAVE ALL sometimes did
not fully clean up properly. (Bug #24901077)
* The Perl path in #! lines at the beginning of Perl
scripts has been adjusted to /usr/local/bin/perl for
FreeBSD 11. (Bug #25719975)
* A race condition could occur for CREATE TABLE statements
with DATA DIRECTORY or INDEX DIRECTORY clauses.
(Bug #25451091)
* Full-text code now uses the standard isalnum() function
rather than the my_isalnum() macro, for improved handling
of default character set structure. (Bug #25447551)
* MySQL compilation in different directories produced
different builds to leakage of absolute paths into debug
information and __FILE__. (Bug #25436469, Bug #84608)
* mysqld_failed to start the server if the --datadir option
was specified with a relative path name. (Bug #25364806)
* With read_only enabled, creation of non-TEMPORARY tables
by non-SUPER users was permitted under certain
conditions. (Bug #25250768)
* mysqlaccess was subject to code injection.
(Bug #25043674)
* On x86 machines, the uint3korr() macro read 4 bytes of
data instead of the intended 3 bytes. (Bug #24807826,
Bug #83264)
* LOAD XML INFILE performance became noticeably slower when
the XML file being read contained a great many spaces,
such as those introduced by indenting or pretty-printing.
Now all leading whitespace is trimmed from each such
value before reading it into memory. (Bug #16212207)
On Behalf of MySQL/ORACLE RE Team
Gipson Pulla
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
