Log message:
Backport section from MySQL 5.7 to fix SunOS/gcc.  PR#51725

Log message:
Changes 5.6.35:

Security Notes
--------------
Incompatible Change: These changes were made to mysqld_safe:
* Unsafe use of rm and chown in mysqld_safe could result in privilege \ 
escalation. chown now can be used only when the target directory is /var/log. An \ 
incompatible change is that if the directory for the Unix socket file is \ 
missing, it is no longer created; instead, an error occurs. Due to these \ 
changes, /bin/bash is required to run mysqld_safe on Solaris. /bin/sh is still \ 
used on other Unix/Linux platforms.
* The --ledir option now is accepted only on the command line, not in option files.
* mysqld_safe ignores the current working directory.

Other related changes:
* Initialization scripts that invoke mysqld_safe pass --basedir explicitly.
* Initialization scripts create the error log file only if the base directory is \ 
/var/log or /var/lib.
* Unused systemd files for SLES were removed.

* MySQL Server now includes a plugin library that enables administrators to \ 
introduce an increasing delay in server response to clients after a certain \ 
number of consecutive failed connection attempts. This capability provides a \ 
deterrent that slows down brute force attacks that attempt to access MySQL user \ 
accounts. For more information, see The Connection-Control Plugin.

* OpenSSL is ending support for version 1.0.1 in December 2016; see \ 
https://www.openssl.org/policies/releasestrat.html. Consequently, MySQL \ 
Commercial Server builds now use version 1.0.2 rather than version 1.0.1, and \ 
the linked OpenSSL library for the MySQL Commercial Server has been updated from \ 
version 1.0.1 to version 1.0.2j. For a description of issues fixed in this \ 
version, see https://www.openssl.org/news/vulnerabilities.html.

This change does not affect the Oracle-produced MySQL Community build of MySQL \ 
Server, which uses the yaSSL library instead.

Functionality Added or Changed
------------------------------
* InnoDB: By default, InnoDB reads uncommitted data when calculating statistics. \ 
In the case of an uncommitted transaction that deletes rows from a table, InnoDB \ 
excludes records that are delete-marked when calculating row estimates and index \ 
statistics, which can lead to non-optimal execution plans for other transactions \ 
that are operating on the table concurrently using a transaction isolation level \ 
other than READ UNCOMMITTED. To avoid this scenario, a new configuration option, \ 
innodb_stats_include_delete_marked, can be enabled to ensure that InnoDB \ 
includes delete-marked records when calculating persistent optimizer statistics. \ 
(Bug 23333990)
* Unit testing now uses Google Mock 1.8. (Bug 24572381, Bug 82823)

Bugs Fixed

Log message:
Changes 5.6.34:
Packaging Notes
---------------
RPM and Debian packages now create the /var/lib/mysql-files directory, which is \ 
now the default value of the secure_file_priv system variable that specifies a \ 
directory for import and export operations.

Security Notes
--------------
Incompatible Change: The secure_file_priv system variable is used to limit the \ 
effect of data import and export operations.

Functionality Added or Changed
------------------------------
yaSSL was upgraded to version 2.4.2. This upgrade corrects issues with: \ 
Potential AES side channel leaks; DSA padding for unusual sizes; the \ 
SSL_CTX_load_verify_locations() OpenSSL compatibility function failing to handle \ 
long path directory names.

Log message:
Ensure upper limit in mysql{56,57}-client respective bl3.

Log message:
Change the way readline/editline support is patched, based on what
mysql57-client has. This fixes at least SmartOS builds, no changes for
NetBSD (and presumably elsewhere).

Log message:
Changes in MySQL 5.6.33 (2016-09-06)

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)

Replication: mysqlbinlog --read-from-remote-server log1 log2 was opening a new \ 
connection for log2 without freeing the connection used for log1. Thanks to \ 
Laurynas Biveinis for the contribution. (Bug 81675, Bug 23540182)

Replication: With binlog_row_image=FULL, when updating single tables temporary \ 
tables were unnecessarily being used. The fix ensures single table update \ 
follows the same pattern as multi-table update. (Bug 79867, Bug 22510353)

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)

Log message:
Changes 5.6.32:
Bugs Fixed

InnoDB: Full-text search auxiliary tables could be dropped by one session while \ 
being access by another.

InnoDB: Selecting full-text index information schema tables for a deleted table \ 
caused a segmentation fault.

InnoDB: Rollback of a full-text index synchronization operation raised an \ 
assertion. The rollback operation attempted to acquire a mutex still held by the \ 
background synchronization thread.

InnoDB: Setting innodb_monitor_enable to all did not enable all counters.

Replication: After issuing a PURGE BINARY LOGS statement, if the binary log \ 
index file was not available, for example because it had been opened by another \ 
application such as MEB, the server could stop unexpectedly. Although this \ 
situation was rare, the handling has been made more robust to avoid unexpected \ 
halts and more informative errors are provided.

Replication: When using row-based replication and InnoDB, replication slaves \ 
reverted to using an older locking scheme when a transaction had already \ 
acquired an AUTOINC lock related to a LOAD FILE or INSERT ... SELECT type of \ 
statement, reducing replication slave performance. The fix ensures that \ 
sql_command is set correctly for any of the DML events such as WRITE_ROWS_EVENT, \ 
UPDATE_EVENT, and DELETE_EVENT.

Replication: A MySQL version 5.5 slave does not have a server_uuid and \ 
replication identified servers by their server_id. Starting from MySQL version \ 
5.6, replication masters detected a zombie dump thread based only on a slave's \ 
server_uuid value, under the assumption that each slave has a unique UUID. \ 
Connecting a MySQL 5.5 slave to a MySQL 5.6 and later master meant that the \ 
master was unable to detect zombie dump threads that were created to serve \ 
slaves running versions older than MySQL 5.6. The fix ensures that a master now \ 
first checks if a slave has a server_uuid set. If it is set, zombie dump thread \ 
detection happens based on the slave's UUID. If a slave's server_uuid is not \ 
set, zombie dump thread detection happens based on server_id.

Replication: With slave_skip_errors enabled there were still special cases when \ 
slave errors were not being correctly ignored. For example:

When opening and locking a table failed.

When field conversions failed on a server running row-based replication.

In these cases the error was considered critical and it was not respecting the \ 
state of slave_skip_errors. The fix ensures that with slave_skip_errors enabled, \ 
all errors reported during applying a transaction are correctly handled. This \ 
means that in such a set up, upon receiving an error with the log_warnings \ 
option set to greater than 1, if the error can be ignored then the warning is \ 
printed into the error log and the server continues as it does in the case of \ 
other ignored errors.

Replication: When using statement-based or mixed binary logging format with \ 
--read-only=ON, it was not possible to modify temporary tables.

MySQL Server upgrades performed using RPM packages failed when upgrading from \ 
MySQL 5.5 Community to MySQL 5.6 Community or MySQL 5.5 Commercial to MySQL 5.6 \ 
Commercial.

The code for reading character set information from Performance Schema statement \ 
events tables (for example, events_statements_current) did not prevent \ 
simultaneous writing to that information. As a result, the SQL query text \ 
character set could be invalid, which could result in a server exit. Now an \ 
invalid character set causes SQL_TEXT column truncation.

A buffer overflow in the regex library was fixed.

Certain arguments to NAME_CONST() could cause a server exit.

For unit-testing with the MySQL test suite, the make unit-test command is no \ 
longer available. The ctest program should be used instead. See Unit Tests Added \ 
to Main Test Runs.

ST_Distance() could raise an assertion for NULL return values.

With the query cache enabled, executing a prepared statement with \ 
CURSOR_TYPE_READ_ONLY and then again with CURSOR_TYPE_NO_CURSOR caused the \ 
server to return an error.

mysql_real_connect() was not thread-safe when invoked with the \ 
MYSQL_READ_DEFAULT_FILE or MYSQL_READ_DEFAULT_GROUP option enabled.

Installing MySQL from a yum or zypper repository resulted in /var/log/mysqld.log \ 
being created with incorrect user and group permissions.

If a stored function updated a view for which the view table had a trigger \ 
defined that updated another table, it could fail and report an error that an \ 
existing table did not exist.

If an INSTALL PLUGIN statement contained invalid UTF-8 characters in the shared \ 
library name, it caused the server to hang (or to raise an assertion in debug \ 
builds).

For multibyte character sets, LOAD DATA could fail to allocate space correctly \ 
and ignore input rows as a result.

Log message:
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.

Log message:
Changes 5.6.31:

Security Notes

The linked OpenSSL library for the MySQL Commercial Server has been updated to \ 
version 1.0.1t. Issues fixed in the new version are described at \ 
http://www.openssl.org/news/vulnerabilities.html.

This change does not affect the Oracle-produced MySQL Community build of MySQL \ 
Server, which uses the yaSSL library instead. (Bug 23229564)

Functionality Added or Changed

A new CMake option, WITH_SYMVER16, if enabled, causes the libmysqlclient client \ 
library to contain extra symbols to be compatible with libmysqlclient on \ 
RHEL/OEL 5, 6, 7, and Fedora releases. All symbols present in \ 
libmysqlclient.so.16 are tagged with symver 16 in libmsqlclient.so.18, making \ 
those symbols have both symver 16 and 18. (Bug 22980983)

support-files/MacOSX/ReadMe.txt is no longer included in MySQL distributions. \ 
(Bug 81038, Bug 23088916)

The version of the tcmalloc library included in MySQL distributions was very \ 
old. It has been removed and is no longer included with MySQL. (Bug 80994, Bug \ 
23068660)

Bugs Fixed

InnoDB: MySQL failed to build on Fedora 24 using GCC 6. (Bug 23227804)

InnoDB: Potential buffer overflow issues were corrected for the InnoDB memcached \ 
plugin. (Bug 23187607)

InnoDB: The full-text index cache was freed during a background index cache \ 
synchronization. (Bug 22996488)

InnoDB: A full-text index operation raised an assertion. (Bug 22963169)

InnoDB: An INSERT operation on a table with a FULLTEXT index and FTS_DOC_ID \ 
column failed because the inserted FTS_DOC_ID value exceeded the permitted gap \ 
between consecutive FTS_DOC_ID values. To avoid this problem, the permitted gap \ 
between the largest used FTS_DOC_ID value and new FTS_DOC_ID value was raised \ 
from 10000 to 65535. (Bug 22679185)

InnoDB: With innodb_autoinc_lock_mode=0, multiple threads waiting for a \ 
table-level lock caused an unexpected deadlock. (Bug 21983865, Bug 78761)

InnoDB: A FLUSH TABLES ... FOR EXPORT operation appeared to stall. A loop in the \ 
ibuf_contract_in_background function failed to exit. (Bug 21133329, Bug 77011)

InnoDB: A full-text query raised an assertion. Under certain circumstances, DDL \ 
operations such as ALTER TABLE ... RENAME caused full-text auxiliary tables to \ 
be removed on server restart. (Bug 13651665)

Replication: In the next_event() function, which is called by a slave's SQL \ 
thread to read the next even from the relay log, the SQL thread did not release \ 
the relaylog.log_lock it acquired when it ran into an error (for example, due to \ 
a closed relay log), causing all other threads waiting to acquire a lock on the \ 
relay log to hang. With this fix, the lock is released before the SQL thread \ 
leaves the function under the situation. (Bug 21697821)

References: See also: Bug 20492319.

Replication: If a multi-threaded replication slave running with \ 
relay_log_recovery=1 stopped unexpectedly, during restart the relay log recovery \ 
process could fail. This was due to transaction inconsistencies not being \ 
filled, see Handling an Unexpected Halt of a Replication Slave. Prior to this \ 
fix, to recover from this situation required manually setting \ 
relay_log_recovery=0, starting the slave with START SLAVE UNTIL \ 
SQL_AFTER_MTS_GAPS to fix any transaction inconsistencies and then restarting \ 
the slave with relay_log_recovery=1. This process has now been automated, \ 
enabling relay log recovery of a multi-threaded slave upon restart \ 
automatically. (Bug 77496, Bug 21507981)

INSERT with ON DUPLICATE KEY UPDATE and REPLACE on a table with a foreign key \ 
constraint defined failed with an incorrect “duplicate entry” error \ 
rather than a foreign key constraint violation error. (Bug 23135731)

References: This issue is a regression of: Bug 78853, Bug 22037930.

For debug builds, CONCAT_WS() could raise an assertion if there was nothing to \ 
append. (Bug 22888420)

Invoking Enterprise Encryption functions in multiple threads simultaneously \ 
could cause a server exit. (Bug 22839278)

Attempting to use Enterprise Encryption functions after creating and dropping \ 
them could cause a server exit. (Bug 22669012)

Setting sort_buffer_size to a very large value could cause some operations to \ 
fail with an out-of-memory error. (Bug 22594514)

An assertion could be raised when a deadlock occurred due to a SELECT ... GROUP \ 
BY ... FOR UPDATE query executed using a Loose Index Scan. (Bug 22187476)

Several potential buffer overflow issues were corrected. (Bug 21977380, Bug \ 
23187436, Bug 23202778, Bug 23195370, Bug 23202699)

If the CA certificate as given to the --ssl-ca option had an invalid path, yaSSL \ 
returned an error message different from OpenSSL. Now both return SSL connection \ 
error: SSL_CTX_set_default_verify_paths failed. (Bug 21920657)

Some string functions returned one or a combination of their parameters as their \ 
result. If one of the parameters had a non-ASCII character set, the result \ 
string had the same character set, resulting in incorrect behavior when an ASCII \ 
string was expected. (Bug 18740222)

On Windows, MySQL installation could result in MySQL being placed under \ 
C:\Program Files\Canon\Easy-WebPrint EX. (Bug 14583183)

References: See also: Bug 70918, Bug 68821, Bug 68227.

On Fedora 24, upgrades using a Community MySQL Server RPM failed to replace an \ 
installed MariaDB Galera server due to a change in the MariaDB package. (Bug \ 
81390, Bug 23273818)

MySQL did not compile under Solaris 12 using Sun Studio. To correct this, \ 
instances of __attribute__ were changed to MY_ATTRIBUTE. (Bug 80748, Bug \ 
22932576)

The INSTALL-SOURCE file had partly outdated information and has been removed \ 
from source packages. (Binary packages are unaffected). (Bug 80680, Bug \ 
23081064)

For a server compiled with -DWITH_PERFSCHEMA_STORAGE_ENGINE=0, a memory leak \ 
could occur for buffered log messages used during server startup. (Bug 80089, \ 
Bug 22578574)

For debug builds, merging a derived table into an outer query block could raise \ 
an assertion. (Bug 79502, Bug 22305361, Bug 21139722)

A null pointer dereference of a parser structure could occur during stored \ 
procedure name validation. (Bug 79396, Bug 22286421)

Using CREATE USER to create an account with the mysql_native_password or \ 
mysql_old_password authentication plugin and using a clause of the form \ 
IDENTIFIED WITH plugin AS 'hash_string' caused the account to be created without \ 
a password. (Bug 78033, Bug 21616496)

Failure of UNINSTALL PLUGIN could lead to inaccurate or confusing errors for \ 
subsequent INSTALL PLUGIN operations. (Bug 74977, Bug 20085672)

mysqld_multi displayed misleading error messages when it was unable to execute \ 
my_print_defaults. (Bug 74636, Bug 19920049)

On Windows, MySQL installation failed if the \ 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ registry \ 
key was present with a key/value pair of "InstallLocation" and \ 
"\Hewlett-Packard\\". (Bug 74631, Bug 19949163)

mysqldump failed silently with no error message when it encountered an error \ 
while executing FLUSH LOGS.

Log message:
Remove stray chunk from patch file. Ride previous revision.