Dear MySQL users,
MySQL Server 5.5.47 is a new version of the 5.5 production release
of the world's most popular open source database. MySQL 5.5.47 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
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.47 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.47 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-47.html
Enjoy!
Changes in MySQL 5.5.47 (2015-12-07)
* Functionality Added or Changed
* Bugs Fixed
Functionality Added or Changed
* MySQL Server RPM packages now contain a conflict
indicator for MySQL Connector C, such that an error
occurs when installing MySQL Server if MySQL Connector C
is also installed. To install MySQL Server, remove any
MySQL Connector C packages first. (Bug #21900800)
* mysql_upgrade now attempts to print more informative
errors than FATAL ERROR: Upgrade failed. (Bug #21489398)
* These client programs now support the
--enable-cleartext-plugin option: mysqlcheck, mysqldump,
mysqlimport, mysqlshow. This option enables the
mysql_clear_password cleartext authentication plugin.
(See The Cleartext Client-Side Authentication Plugin
(http://dev.mysql.com/doc/refman/5.5/en/cleartext-authentication-plugin.html).)
(Bug #21235226)
Bugs Fixed
* InnoDB: Altering the letter case of a column introduced
an inconsistency between the frm file and data dictionary
resulting in a failed CREATE INDEX operation on the
altered column. (Bug #20755615)
* MySQL development RPM packages could fail to install if
MySQL Connector/C development RPM packages were
installed. (Bug #22005375)
* Possible buffer overflow from incorrect use of strcpy()
and sprintf() was corrected. (Bug #21973610)
* MySQL RPM packages for RHEL5 failed to create the mysql
system user. (Bug #21950975)
* Concurrent FLUSH PRIVILEGES and REVOKE or GRANT
statements could produce a small time window during which
invalid memory access to proxy user information could
occur, leading to a server exit. (Bug #21602056)
* Starting the server with the query_alloc_block_size
system variable set to certain negative values on a
machine without enough memory could result in
out-of-memory errors. (Bug #21503595)
* Using UNINSTALL PLUGIN to uninstall the daemon_example
plugin could cause a server exit. (Bug #21467458)
* FLUSH DES_KEY_FILE failed to reload the DES key file.
(Bug #21370329)
* A server exit could occur for the second execution of a
prepared statement for which an ORDER BY clause referred
to a column position. (Bug #20755389)
* Repeated execution of a prepared statement could cause a
server exit if the default database was changed. (Bug
#20447262)
* Outer references do not work as arguments to MATCH(), but
the server did not properly detect them. Now it does and
raises an error. (Bug #20007383)
References: See also Bug #21140088.
* Valgrind errors were produced during row comparator
setup. (Bug #19929406)
* INSERT DELAYED could cause a server exit for tables
partitioned with a character column as the key and for
which the expression required a character set conversion.
(Bug #19894161)
* A server exit could occur when updating a view using an
ALL comparison operator on a subquery that selects from
an indexed column in the main table. (Bug #19434916)
* When a fixed-width row was inserted into a MyISAM
temporary table, the entire content of the record buffer
was written to the table, including any trailing space
contained in VARCHAR columns, the issue being that this
trailing space could be uninitialized. This problem has
been resolved by insuring that only the bytes actually
used to store the VARCHAR (and none extra) are copied and
inserted in such cases. (Bug #13389854, Bug #22123583)
* Temporary MyISAM tables (unlike normal MyISAM tables) did
not use the dynamic row format when they contained
VARCHAR columns, resulting in larger temporary files (and
more file I/O) than necessary. (Bug #13350136, Bug
#22023218)
On behalf of Oracle MySQL Release Engineering Team,
Gipson Pulla
↧
MySQL Community 5.5.47 Server has been released (no replies)
↧