Log message:
Skip interpreter check for a python test script.

Log message:
The postinstall-solaris script is still being installed on SunOS.

Log message:
fix SMF Manifest installation by not overwriting INSTALLATION_DIRS

Log message:
Changes 5.6.19:
Functionality Added or Changed

The obsolete and unmaintained charset2html utility has been removed from MySQL \ 
distributions.

The mysqlbug, mysql_waitpid, and mysql_zap utilities have been deprecated and \ 
will be removed in MySQL 5.7.

Bugs Fixed

InnoDB: After upgrading from 5.6.10 to MySQL versions up to and including MySQL \ 
5.6.18, InnoDB would attempt to rename obsolete full-text search auxiliary \ 
tables on server startup, resulting in an assertion failure.

InnoDB: For each insert, memset would be called three times to allocate memory \ 
for system fields. To reduce CPU usage, the three memset calls are now combined \ 
into a single call.

InnoDB: Enabling the InnoDB Table Monitor would result in a \ 
ib_table->stat_initialized assertion failure.

InnoDB: Setting innodb_max_dirty_pages_pct=0 would leave 1% of dirty pages \ 
unflushed. Buffer pool flushing is initiated when the percentage of dirty pages \ 
is greater innodb_max_dirty_pages_pct. The internal variables that store the \ 
innodb_max_dirty_pages_pct value and the percentage of dirty pages \ 
(buf_get_modified_ratio_pct and srv_max_buf_pool_modified_pct) were defined as \ 
unsigned integer data types, which meant that a innodb_max_dirty_pages_pct value \ 
of 0 required a dirty pages percentage of 1 or greater to initiate buffer pool \ 
flushing.

To address this problem, the buf_get_modified_ratio_pct and \ 
srv_max_buf_pool_modified_pct internal variables are redefined as double data \ 
types, which changes the range value for innodb_max_dirty_pages_pct and \ 
innodb_max_dirty_pages_pct_lwm from 0 .. 99 to 0 .. 99.99. Additionally, buffer \ 
pool flushing is now initiated when the percentage of dirty pages is \ 
“greater than or equal to” innodb_max_dirty_pages_pct.

Replication: Log rotation events could cause group_relay_log_pos to be moved \ 
forward incorrectly within a group. This meant that, when the transaction was \ 
retried, or if the SQL thread was stopped in the middle of a transaction \ 
following one or more log rotations (such that the transaction or group spanned \ 
multiple relay log files), part or all of the group was silently skipped.

This issue has been addressed by correcting a problem in the logic used to avoid \ 
touching the coordinates of the SQL thread when updating the log position as \ 
part of a relay log rotation whereby it was possible to update the SQL thread's \ 
coordinates when not using a multi-threaded slave, even in the middle of a \ 
group.

Replication: When running the server with --gtid-mode=ON, STOP SLAVE followed by \ 
START SLAVE resulted in a mismatch between the information provided by \ 
INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO and the Slave_open_temp_tables status \ 
variable: the INNODB_TEMP_TABLE_INFO table showed that no temporary tables \ 
existed, but Slave_open_temp_tables had a nonzero value.

Replication: In certain cases, the server mishandled triggers and stored \ 
procedures that tried to modify other tables when called by CREATE TABLE ... \ 
SELECT. This is now handled correctly as an error.

Replication: When used on a table employing a transactional storage engine, a \ 
failed TRUNCATE TABLE was still written to the binary log and thus replayed on \ 
the slave. This could lead to inconsistency when the master retained data that \ 
was removed on the slave.

Now in such cases TRUNCATE TABLE is logged only when it executes successfully.

Replication: The server did not always handle the auto.cnf file correctly in \ 
cases where this file's permissions were incorrect.

Replication: When the binary log was rotated due to receipt of a SIGHUP signal, \ 
the new binary log did not contain the Previous_gtid_event required for \ 
subsequent processing of that binary log's GTID events. Now when SIGHUP is \ 
received, steps are taken to insure that the server writes the necessary \ 
Previous_gtid_event to the new log before writing any GTID events to the new \ 
log.

Log message:
Don't hardcode PID file. Instead, give the user the option to set it. The
rc.d script overrides my.cnf directives. Hardcoding the PID can cause a
problem on systems transitioning to MySQL packages from pkgsrc.

Log message:
Changes 5.6.17:

Functionality Added or Changed

Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit \ 
control of the block encryption mode and take an optional initialization vector \ 
argument:

The new block_encryption_mode system variable controls the mode for block-based \ 
encryption algorithms. Its default value is aes-128-ecb, which signifies \ 
encryption using a key length of 128 bits and ECB mode.

An optional init_vector argument provides an initialization vector for \ 
encryption modes that require it:

AES_ENCRYPT(str,key_str[,init_vector])
AES_DECRYPT(crypt_str,key_str[,init_vector])
A random string of bytes to use for the initialization vector can be produced by \ 
calling the new RANDOM_BYTES() function.

For more information, see Encryption and Compression Functions.

These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe for \ 
statement-based replication and they cannot be stored in the query cache. \ 
Queries that use RANDOM_BYTES() are unsafe for statement-based replication and \ 
cannot be stored in the query cache.

Incompatible Change: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and \ 
NO_ZERO_IN_DATE SQL modes now are deprecated and setting the sql_mode value to \ 
include any of them generates a warning. In MySQL 5.7, these modes do nothing. \ 
Instead, their effects are included in the effects of strict SQL mode \ 
(STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The motivation for the change in \ 
MySQL 5.7 is to reduce the number of SQL modes with an effect dependent on \ 
strict mode and make them part of strict mode itself.

To make advance preparation for an upgrade to MySQL 5.7, see SQL Mode Changes in \ 
MySQL 5.7. That discussion provides guidelines to assess whether your \ 
applications will be affected by the SQL mode changes in MySQL 5.7.

InnoDB: MySQL now supports rebuilding regular and partitioned InnoDB tables \ 
using online DDL (ALGORITHM=INPLACE) for the following operations:

OPTIMIZE TABLE

ALTER TABLE ... FORCE

ALTER TABLE ... ENGINE=INNODB (when run on an InnoDB table)

Online DDL support reduces table rebuild time and permits concurrent DML, which \ 
helps reduce user application downtime. For additional information, see Overview \ 
of Online DDL.

On Solaris, mysql_config --libs now includes -R/path/to/library so that \ 
libraries can be found at runtime.

mysql_install_db provides a more informative diagnostic message when required \ 
Perl modules are missing.

The IGNORE clause for ALTER TABLE is now deprecated and will be removed in a \ 
future version of MySQL. ALTER IGNORE TABLE causes problems for replication, \ 
prevents online ALTER TABLE for unique index creation, and causes problems with \ 
foreign keys (rows removed in the parent table).

Bugs Fixed

Log message:
Fix SMF_METHOD_FILE expansion.

Log message:
Import initial SMF support for individual packages.

Log message:
Remove example rc.d scripts from PLISTs.

These are now handled dynamically if INIT_SYSTEM is set to "rc.d", or
ignored otherwise.

Log message:
Changes 5.6.16:
Functionality Added or Changed
* InnoDB: New global configuration parameters, innodb_status_output and \ 
innodb_status_output_locks, allow you to dynamically enable and disable the \ 
standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling \ 
and disabling monitors for periodic output by creating and dropping specially \ 
named tables is deprecated and may be removed in a future release.
* Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result \ 
had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old \ 
temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD \ 
INDEX, and FORCE operations. This conversion cannot be done using the INPLACE \ 
algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error.
* CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir \ 
value. If unspecified, the value defaults to P_tmpdir in <stdio.h>.

Bugs Fixed
* InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration \ 
with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak \ 
memory.
* InnoDB: A boolean mode full-text search query would result in a memory access \ 
violation during parsing.
* InnoDB: When new indexes are added by an ALTER TABLE operation, instead of \ 
only saving table-level statistics and statistics for the new indexes, InnoDB \ 
would save statistics for the entire table, including the table's other indexes. \ 
This behavior slowed ALTER TABLE performance.
* InnoDB: Due to a parser error, full-text search queries that include a \ 
sub-expression could return the wrong result.
* InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve \ 
file size information, which resulted in an incorrect error message (Error: \ 
ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was \ 
exceeded. innochecksum now provides support for files larger than 2GB in both \ 
MySQL 5.6 and MySQL 5.7.
* InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was \ 
not allocated for the default memcached engine when using the default memcached \ 
engine as the backstore for data instead of InnoDB.
* InnoDB: InnoDB would report an incorrect operating system error code after \ 
failing to initialize.
* InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE \ 
... DISCARD TABLESPACE could result in a serious error.
* InnoDB: Persistent optimizer statistics would cause stalls due to latch contention.
* InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for \ 
AGAINST() could result in an error when run on an InnoDB table with a full-text \ 
search index.
* InnoDB: An InnoDB full-text search failure would occur due to an \ 
“unended” token. The string and string length should be passed for \ 
string comparison.
* InnoDB: In debug builds, a merge insert buffer during a page read would cause \ 
a memory access violation.
* InnoDB: Truncating a memcached InnoDB table while memcached is performing DML \ 
operations would result in a serious error.
* InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call \ 
os_thread_get_curr_id.
* InnoDB: Attempting to rename a table to a missing database would result in a \ 
serious error.
more...