After upgrading the server many users start it with an unchanged config file only to find some deprecated options that they were using are no longer supported by the later server version, which causes the upgraded server to shutdown. In other cases modifying the server configuration file results in the server refusing to start when an invalid name is mistakenly entered in the configuration file.…
All posts by Nisha Gopalakrishnan
Upgrading to MySQL 8.0? Here is what you need to know…
In my previous blog post, I had described the steps to perform an in-place upgrade for upgrading from MySQL 5.7 to MySQL 8.0. In this blog post, I will discuss about the considerations that needs to be taken into account while upgrading to MySQL 8.0
The general in-place upgrade requirement is that MySQL 8.0 will understand the disk image produced by MySQL 5.7. …
INPLACE upgrade from MySQL 5.7 to MySQL 8.0
MySQL 8.0 General Availability was announced in April and it comes with a host of new features. The overview about the new features and improvements made in MySQL 8.0 can be found in the following blog.
The server can be upgraded by performing either an INPLACE upgrade or LOGICAL upgrade. …
Improvements to XA Support in MySQL 5.7
Introduction
XA stands for “eXtended Architecture”, and is a standard created by The Open Group for distributed transaction processing. While MySQL 5.0 was the first version to support XA, MySQL 5.7 has removed major limitations, fixed a number of bugs, and increased overall test-case coverage.…
How to Easily Identify Tables With Temporal Types in Old Format!
The MySQL 5.6.4 release introduced support for fractional values within the temporal datatypes: TIME, DATETIME, and TIMESTAMP. Hence the storage requirement and encoding differs for them in comparison to older (5.5 and earlier) temporal datatypes. The storage format for the temporal datatypes in the old format are not space efficient either, and recreating tables having both the new and old formats can be a long and tedious process.…
MySQL 5.6.17: Improved Online Optimize Table For INNODB and PARTITIONED INNODB Tables
OPTIMIZE TABLE is a maintenance operation used to recover the disk space and improve IO efficiency. It is recommended that the operation is carried out under the cases noted in the optimize table documentation.
MySQL versions prior to MySQL 5.6.17 does not allow concurrent changes (inserts, updates, deletes) to the table when the OPTIMIZE TABLE operation is being performed on that table.…
Upgrading old MySQL-5.5 format temporals to MySQL-5.6 format.
The temporal datatypes ‘TIME/DATETIME/TIMESTAMP’ supports fractional values starting from MySQL 5.6.4 version. Hence the storage requirement and encoding differs in comparison to pre- MySQL 5.6.4 temporal datatypes.
As mentioned in the section ‘Upgrading from MySQL 5.5 to 5.6’,
http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html
Once you have imported the pre-MySQL 5.6.4 tables, ‘ALTER TABLE’ allows creation of tables containing temporal columns of both mysql-5.5 and mysql-5.6 format.…