Dear MySQL users,

MySQL Server 5.6.33, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.6.33 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.6, please see

http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html

Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6
are available both as a "full" installer and as a "web" installer.
The full installer is significantly larger and comes bundled with
the latest software releases available. This bundle makes it easy
to download and configure a full server and development suite.

The web installer doesn't come bundled with any actual products
and instead relies on download-on-demand to fetch only the
products you choose to install. This makes the initial download
much smaller but increases install time as the individual products
will need to be downloaded.

For information on installing MySQL 5.6.33 on new servers or upgrading
to MySQL 5.6.33 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.6/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

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:

https://wikis.oracle.com/display/mysql/Contributing

The following section lists the changes in the MySQL 5.6 since
the release of MySQL 5.6.32. It may also be viewed
online at

http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-33.html

Enjoy!


==============================================================================

Changes in MySQL 5.6.33 (2016-09-06)


* Test Suite Notes

* Functionality Added or Changed

* Bugs Fixed

Test Suite Notes

* In mysql-test-run.pl, a limit of 50 was imposed on the
number of workers for parallel testing, which on systems
with more than 50 CPUs resulted in exhaustion of unique
thread IDs. The ID-exhaustion problem has been corrected,
and the limit of 50 on number of workers has been lifted.
Thanks to Daniel Black for the patch on which this change
was based. Additionally, these changes were made:

+ To avoid idle workers, the number of parallel
workers now is limited to the number of tests.

+ Previously, if --parallel=auto was given and the
MTR_MAX_PARALLEL environment variable was not set, a
limit of 8 was imposed on the number of parallel
workers. This limit has been lifted.
(Bug #22342399, Bug #79585)

Functionality Added or Changed

* CMake support for compiling with Solaris Studio 12.5 was
added. (Bug #82249, Bug #24303829, Bug #81274, Bug
#23212938)

Bugs Fixed

* InnoDB: An operation that dropped and created a full-text
search table raised an assertion. (Bug #24315031)

* InnoDB: Accessing full-text search auxiliary tables while
dropping the indexed table raised an assertion. (Bug
#24009272)

* InnoDB: An online DDL operation on a table with indexed
BLOB columns raised an assertion during logging of table
modifications. (Bug #23760086)

* For mysqld_safe, the argument to --malloc-lib now must be
one of the directories /usr/lib, /usr/lib64,
/usr/lib/i386-linux-gnu, or /usr/lib/x86_64-linux-gnu. In
addition, the --mysqld and --mysqld-version options can
be used only on the command line and not in an option
file. (Bug #24464380)

* It was possible to write log files ending with .ini or
.cnf that later could be parsed as option files. The
general query log and slow query log can no longer be
written to a file ending with .ini or .cnf. (Bug
#24388753)

* Privilege escalation was possible by exploiting the way
REPAIR TABLE used temporary files. (Bug #24388746)

* If the basedir system variable was set at server startup
from the command line or option file, the value was not
normalized (on Windows, / was not replaced with /). (Bug
#23747899, Bug #82125)

* In-place ALTER TABLE operations which when executed
separately caused no table rebuild could when combined
into a single statement result in a table rebuild. (Bug
#23475211, Bug #81587)

* A blank server name in CREATE SERVER statements produced
a server exit rather than an error. (Bug #23295288)

* A prepared statement that used a parameter in the select
list of a derived table that was part of a join could
cause a server exit. (Bug #22392374, Bug #24380263)

* MEDIUMINT columns used in operations with long integer
values could result in buffer overflow. (Bug #19984392)

* A spurious ER_NO_SUCH_TABLE error could occur when
attempting to execute a prepared CREATE TABLE ... SELECT
statement that used a temporary table in the FROM clause
and called a stored function. The same error could occur
for a nonprepared version of the statement if used in a
stored procedure when the procedure was re-executed. (Bug
#16672723, Bug #68972)

* EINTR handling in the client library has been fixed so
that interrupted read and write calls are retried.
Previously, EINTR was ignored. (Bug #82019, Bug
#23703570)

On Behalf of MySQL Release Engineering
Prashant Tekriwal