diff options
| author | adam <adam> | 2013-09-30 18:26:38 +0000 |
|---|---|---|
| committer | adam <adam> | 2013-09-30 18:26:38 +0000 |
| commit | d56670155519668734440ed44e1c377479859e04 (patch) | |
| tree | c443d27e2b55e696c9cc63f2bb2b4f658a1fa709 /databases/mysql55-server | |
| parent | 59ba2e391a0d4dfc10777bc2c34bf92360e9cbb0 (diff) | |
| download | pkgsrc-d56670155519668734440ed44e1c377479859e04.tar.gz | |
Changes 5.5.34:
* 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.5 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.
* 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: 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: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write.
* InnoDB: A regression introduced with the fix for Bug 11762038 would cause InnoDB to raise an incorrect error message. The message stated that, “InnoDB cannot delete/update rows with cascading foreign key constraints that exceed max depth of 20”. The error message would occur when killing connections reading from InnoDB tables that did not have foreign key constraints.
* InnoDB: The documentation incorrectly stated that START TRANSACTION WITH CONSISTENT SNAPSHOT provides a consistent snapshot only if the current isolation level is REPEATABLE READ or SERIALIZABLE. START TRANSACTION WITH CONSISTENT SNAPSHOT only works with REPEATABLE READ. All other isolation levels are ignored. The documentation has been revised and a warning is now generated whenever the WITH CONSISTENT SNAPSHOT clause is ignored.
* InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping.
more...
Diffstat (limited to 'databases/mysql55-server')
| -rw-r--r-- | databases/mysql55-server/PLIST | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/databases/mysql55-server/PLIST b/databases/mysql55-server/PLIST index 6472f767e91..96641eb8171 100644 --- a/databases/mysql55-server/PLIST +++ b/databases/mysql55-server/PLIST @@ -1,4 +1,4 @@ -@comment $NetBSD: PLIST,v 1.23 2013/06/04 13:31:21 adam Exp $ +@comment $NetBSD: PLIST,v 1.24 2013/09/30 18:26:38 adam Exp $ bin/innochecksum bin/my_print_defaults bin/myisam_ftdump @@ -435,6 +435,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/implicit_commit_helper.inc share/mysql/test/include/index_merge1.inc share/mysql/test/include/index_merge2.inc |