CVS commit: pkgsrc/databases

["Adam Ciarcinski" <adam%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   adam
Date:           Sat Oct  3 12:13:29 UTC 2015

Modified Files:
        pkgsrc/databases/mysql55-client: Makefile.common distinfo options.mk
        pkgsrc/databases/mysql55-server: PLIST

Log Message:
Changes 5.5.46:
* yaSSL was upgraded to version 2.3.8.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong 
tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.
* Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected.
* Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE.
* Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit.
* mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the 
file.)
* An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback.
* Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup.
* For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition.
* DELETE could check privileges for the wrong database when table aliases were used.
* Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit.
* MySQL sometimes produced no warning when it was unable to interpret a character in a given character set.
* For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit.
* Execution of certain BINLOG statements while temporary tables were open by HANDLER statements could cause a server exit.


To generate a diff of this commit:
cvs rdiff -u -r1.46 -r1.47 pkgsrc/databases/mysql55-client/Makefile.common
cvs rdiff -u -r1.44 -r1.45 pkgsrc/databases/mysql55-client/distinfo
cvs rdiff -u -r1.9 -r1.10 pkgsrc/databases/mysql55-client/options.mk
cvs rdiff -u -r1.37 -r1.38 pkgsrc/databases/mysql55-server/PLIST

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.