[atomic] Mysql 5.5.17

Atomic repository announcements, new release notifications and other news regarding the atomic yum repository.
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin
Posts: 8330
Joined: Wed Dec 31, 1969 8:00 pm
Location: earth

[atomic] Mysql 5.5.17

Unread post by scott »

+ Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. (Bug #12897501)
+ MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. (Bug #51655, Bug #11759349)
- InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. (Bug #12950803, Bug #62294)
- InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. (Bug #12704861)
- InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. (Bug #12601439)
- InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) (Bug #11766591, Bug #59733)
- Internal conversion of zero to binary and back could yield a result with incorrect precision. (Bug #12911710)
- Valgrind warnings generated by filesort operations were fixed. (Bug #12856915)
- mysqld_safe did not properly check for an already running instance of mysqld. (Bug #11878394)
- The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. (Bug #58898, Bug #11765888)
- An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. (Bug #58200, Bug #11765254)
- myisampack could create corrupt FULLTEXT indexes when compressing tables. (Bug #53646, Bug #11761180)
- A linking problem prevented the FEDERATED storage engine plugin from loading. (Bug #40942, Bug #11750417)

[+] New Feature [=] Update [-] Bugfix

To upgrade:
yum upgrade mysql
Post Reply