How to select the most stable MySQL version

Document directory

• MySQL database GA version selection process

MySQL open-source database has multiple important branches: MySQL Cluster, MySQL 5.1, MySQL 5.5, and MySQL 6.2. Each branch has the same MySQL database version: Development version, Alpha version, Beta version, RC version, and GA version.

The Development version, Alpha version, and Beta version are generally not used in the project. Because they certainly have major problems or some functions are not fully implemented. In most cases, the RC version is not allowed to be used in the production environment. After all, it is only a small version before the production version is released. Similarly,We should also carefully choose the GA version of the MySQL database.. After all, open-source community products have not been strictly tested and may have weak stability than commercial products.

MySQL database GA version selection process

Since Oracle acquired SUN and its wholly-owned subsidiary MySQL AB, MySQL AB has no longer contributed source code to the open-source community. At the same time, as many founders and technicians leave,Everyone must carefully select the new version released by MySQL AB. Do not blindly trust the test report officially provided by MySQL AB. We recommend that you refer to the following MySQL database ga version selection process::

• Analyze whether the enterprise business needs to use the basic functions and features of MySQL. The key features are as follows:MySQL replication, partition tables, Plugin-InnoDB, etc..
• The first ga version of the MySQL database product line was released,It takes at least 10 months to use it in the production environment..
• The latest ga version of the MySQL database product line,Generally, it is not the preferred target., You can consider 3 ~ later than the latest version ~ Four versions of GA databases.
• Read the GA version of the target database carefully. If a large number of bugs are modified based on the previous version, the GA version should be carefully selected.
• Carefully read the information of the first version after the GA version of the target database,If the BUG information to be modified is large, discard the target version.To forward a version number to the target version.
• Follow the steps described in step 4 and Step 5 to select a version that is later than the selected version. The number of bugs is not significant, and there are very few serious bugs, and it is not the latest ga version.
• Read in detail 2 ~ after the selected database ga version ~ The bug fix information of the three versions is mainly related to the target ga version, and how to reproduce it and find solutions to circumvent it.
• For the GA version selected in the above seven steps,Functional testing and performance testing are required in combination with functions that may be required by enterprise businesses..
• The selected database ga version, as an internal development and testing database environment, usually takes about 3-6 months for trial run.
• The new GA version can be considered for non-core businesses of enterprises.
• After the above 10 procedures, if there are no major functional bugs or performance bottlenecks, you can start to consider as the backend database of all business data services.

Many full-time DBAs in enterprises may not have the time, energy, or resources to select versions, and may not be willing to spend so much time. Some enterprises may need to select a database GA version. Some enterprises do not have a full-time DBA, but are replaced by O & M or development engineers, however, they may not be able to select database software versions. Are there any shortcuts for choosing the GA version of the MySQL database? The answer is yes.You can pay more attention to the DBAs of some major companies or well-known DBAs in the industry and consult them through multiple channels.Or you can consult an internal user to know the version of their core business database.