![]() There are ways to install MySQL 5.5 which we will see in later articles. MySQL Community Server 5.5.In this article, we will go through one of the multiple ways to install MySQL 5.5 Server on CentOS 7 through YUM utility. * mysqlbinlog did not accept input on the standard input when the standard input was a pipe. * Adding a LIMIT clause to a query containing GROUP BY and ORDER BY could cause the optimizer to choose an incorrect index for processing the query, and return more rows than required. The resulting connection used SSL, but the key was not used. * The argument to the -ssl-key option was not verified to exist and be a valid key. * mysqlhotcopy failed for databases containing views. * A query for a FEDERATED table could return incorrect results when the underlying table had a compound index on two columns and the query included an AND condition on the columns. * CHECK TABLE and REPAIR TABLE could crash if a key definition differed in the. * The Thread Pool plugin did not respect the wait_timeout timeout for client sessions. * The argument for LIMIT must be an integer, but if the argument was given by a placeholder in a prepared statement, the server did not reject noninteger values such as '5'. If a program linked against that library and libcurl, it could crash with a segmentation fault. * The libmysqlclient_r client library exported symbols from yaSSL that conflict with OpenSSL. * The RPM spec file now also runs the test suite on the new binaries, before packaging them. * Replication: In master-master replication with -log-slave-updates enabled, setting a user variable and then performing inserts using this variable caused the Exec_master_log_position column in the output of SHOW SLAVE STATUS not to be updated. This caused LOAD DATA INFILE to fail when trying to load a file larger than 4G in size, even when max_binlog_cache_size was set to a value greater than this. * Replication: On 64-bit Windows platforms, values greater than 4G for the max_binlog_cache_size and max_binlog_stmt_cache_size system variables were truncated to 4G. As part of this fix, memory is now allocated for reading from rows only in partitions that have not been pruned. This issue has been addressed by allocating buffers for reads from partitioned tables only when they are needed and freeing them immediately once they are no longer needed. For SELECT statements on tables with many partitions and large rows, this could cause the server to use excessive amounts of memory. * Partitioning: The buffer for the row currently read from each partition used for sorted reads was allocated on open and freed only when the partitioning handler was closed or destroyed. ![]() This issue is resolved by ensuring that partition pruning skips any remaining partitioning key columns once a partition key column that cannot be used in pruning is encountered. ![]() ) PARTITION BY KEY() # Use primary key as partitioning key > The WHERE condition used with the last column of the partitioning key was satisfied only by a single value, while the condition testing some previous column from the partitioning key was satisfied by a range of values.Īn example of a statement creating a partitioned table and a query against this for which the issue described above occurred is shown here: FOR UPDATE, UPDATE, or other SQL statement scanned rows in an InnoDB table using a The columns making up the table's partitioning key were used in the same order as in the partitioning key definition by a SELECT statement's WHERE clause as in the column definitions * InnoDB: Certain information_schema tables originally introduced in MySQL 5.6 are now also available in MySQL 5.5 and MySQL 5.1: INNODB_BUFFER_PAGE, INNODB_BUFFER_PAGE_LRU, and INNODB_BUFFER_POOL_STATS. Old versions of the plugin will work with current versions of the server, but versions of the server older than 5.5.28 will not work with current versions of the plugin. * The internal interface of the Thread Pool plugin has changed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |