diff options
| author | adam <adam> | 2013-10-01 10:26:39 +0000 |
|---|---|---|
| committer | adam <adam> | 2013-10-01 10:26:39 +0000 |
| commit | 8b9e86ed0c9f9bc4a21713a39ea9c898dfefb065 (patch) | |
| tree | 494ecb4b478760ea3dbfaa40d83560ad75fdb25f /databases/mysql56-server | |
| parent | 616a50de27383f778a0fd056245539928f6fbe73 (diff) | |
| download | pkgsrc-8b9e86ed0c9f9bc4a21713a39ea9c898dfefb065.tar.gz | |
Changes 5.6.14:
* MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.6 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File.
* Important Change; Replication: START SLAVE UNTIL SQL_AFTER_GTIDS did not cause the slave to stop until the next GTID event was received following execution of the transaction having the indicated GTID, which could cause issues in the case when the next GTID event is delayed, or does not exist. Now the slave stops after completing the transaction with that GTID.
* InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows.
* InnoDB: When logging the delete-marking of a record during online ALTER TABLE...ADD PRIMARY KEY, InnoDB writes the transaction ID to the log as it was before the deletion or delete-marking of the record. When doing this, InnoDB would overwrite the DB_TRX_ID field in the original table, which could result in locking issues.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: An assertion would be raised in fil_node_open_file due to a missing .ibd file. Instead of asserting, InnoDB should return false and the caller of fil_node_open_file should handle the return message.
* InnoDB: The assertion ut_ad(oldest_lsn <= cur_lsn) in file buf0flu.cc would fail because the current max LSN would be retrieved from the buffer pool before the oldest LSN.
* InnoDB: InnoDB memcached add and set operations would perform more slowly than SQL INSERT operations.
* InnoDB: The InnoDB memcached plugin could be initialized to insert into an InnoDB table with an INTEGER primary key.
More...
Diffstat (limited to 'databases/mysql56-server')
| -rw-r--r-- | databases/mysql56-server/PLIST | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/databases/mysql56-server/PLIST b/databases/mysql56-server/PLIST index f7e780fcf04..40eecd47399 100644 --- a/databases/mysql56-server/PLIST +++ b/databases/mysql56-server/PLIST @@ -1,4 +1,4 @@ -@comment $NetBSD: PLIST,v 1.4 2013/07/31 09:51:38 adam Exp $ +@comment $NetBSD: PLIST,v 1.5 2013/10/01 10:26:39 adam Exp $ bin/innochecksum bin/my_print_defaults bin/myisam_ftdump @@ -501,6 +501,7 @@ share/mysql/test/include/have_utf16.inc share/mysql/test/include/have_utf32.inc share/mysql/test/include/have_utf8.inc share/mysql/test/include/have_utf8mb4.inc +share/mysql/test/include/have_valgrind.inc share/mysql/test/include/have_validate_password_plugin.inc share/mysql/test/include/ib_logfile_size_check.inc share/mysql/test/include/icp_tests.inc |