MySQL server stability

This article answers the following question: "How stable is the MySQL server ?", And "can I rely on the MySQL server in this project "? We will try to clarify this type of questions and answer some important questions that may concern many potential users. The information provided in this section is based on the data collected through the mail list. The Mail List is useful in identifying problems and reporting usage types.

The initial code can be traced back to the beginning of 1980s. It provides a stable encoding base, and the ISAM table format used by the storage engine remains backward compatible. In TcX, the predecessor of MySQL AB, MySQL code has worked well in multiple projects since the middle of 1996 and has not encountered any problems. When the MySQL database software was first released to the wider public, our users quickly found some untested code segments. Since then, although each new version has many new features, each new version has a small number of portability problems.

Each released MySQL server is available. The problem only occurs when the user tries to source the code from the "gray area. Of course, new users do not know what the "gray area" is. Therefore, this article describes the regions that are currently known. This section describes MySQL Server version 3.23 and later. In the latest version, all known and reported defects are corrected, except as listed in section "defects", which are associated with design.

The MySQL server adopts multi-layer design and independent modules. Some newer modules are listed here and their testing conditions are described.

Replication (stable)

A large number of servers that use the replication function are in the production mode and the results are good. In MySQL 5.x, the replication function will be enhanced.

InnoDB table (stable)

Since version 3.23.49, the InnoDB Transaction storage engine has been stable. InnoDB is used in large and heavy load production systems.

BDB table (stable)

The Berkeley DB code is very stable, but we are still improving the BDB transaction storage engine on the MySQL server.

Full text search (stable)

Full text search is widely used. Important feature enhancements are added to MySQL 4.0 and 4.1.

MyODBC 3.51 (stable)

MyODBC 3.51 uses odbc sdk 3.51 and is widely used in production activities. Some situations may seem to be related to the application, not the ODBC driver or the underlying database server.