MySQL Server Versions

With the new MySQL versioning model as of July 2023, you have the flexibility to select between two release tracks, Innovation or Long-Term-Support (LTS)/Bugfix, depending on your application and environment needs. Both of the release tracks are production-grade quality and supported by MySQL HeatWave Service.

Supported MySQL Server Versions

MySQL server versions are divided into Innovation track and LTS/BugFix track.

Innovation Track

If you desire access to the latest features and improvements and enjoy staying on top of the latest technologies, then MySQL innovation track is the best fit for you. This is ideal for developers and database administrators working in fast-paced environments with high levels of automated tests and modern continuous integration techniques for faster upgrade cycles. For example, MySQL 8.1.0 is the first innovation release. If you want the latest features, improvements, and all bug fixes for the MySQL database, use the innovation release track, 8.1.x, 8.2.x, 8.3.x, and so on.

LTS/BugFix Track

LTS/Bugfix track contains only necessary fixes, so it is a better choice if your environment requires established database software behavior. Features can be removed and added only in the first version of a LTS release (such as 8.4.0 LTS) but not later versions (such as 8.4.1 LTS and 8.4.2 LTS) in the same LTS release. For MySQL 8.0, 8.0.34 is the first Bugfix version where no features will be removed and added in subsequent versions (such as 8.0.35 and 8.0.36) in the 8.0 release.

MySQL Versions Deprecation and Removal Policy in MySQL HeatWave Service

Older MySQL versions are marked as deprecated approximately three months before they become unavailable in MySQL HeatWave Service. Any DB system running a deprecated version is upgraded automatically in its next maintenance window after the unavailable date.

The MySQL HeatWave Service begins supporting new MySQL Server versions as soon as they are released as Generally Available (GA).

Customers are advised to regularly update their DB systems to the latest GA version. This can be from either the Innovation or LTS/Bugfix track. Regular updates ensure access to the latest features, bug fixes, and security patches. To update the MySQL Server version of a DB system, see Editing a DB System.

Each MySQL version in the LTS/Bugfix track will be deprecated about one year after its GA date while each MySQL version in the Innovation track will be deprecated about three months after its GA date. A notification banner will appear in the DB system details when you are running a deprecated version of MySQL Server. We strongly recommend updating and testing your DB systems when a MySQL server version has been deprecated.

About three months after the deprecation date, the MySQL server version will be unavailable. Any DB system that is still running an unavailable version will be upgraded automatically in its next maintenance window.

MySQL Version Support Schedule in MySQL HeatWave Service

Each MySQL version is released on its General Availability date and is deprecated before it is made unavailable.

Note

Dates indicated by only month and year are preliminary and will be updated to specific dates as soon as they're confirmed.

The mentioned dates are exclusive to the cloud service version. For details regarding MySQL Community, Enterprise, and CGE editions, please refer to the MySQL release notes documentation.

Table 5-6 MySQL 8.0 Release Schedule in MySQL HeatWave Service

Version General Availability (GA) date Deprecation date Unavailable date
8.0.31 October 28, 2022 October 25, 2023 January 16, 2024
8.0.32 February 8, 2023 January 16, 2024 April 16, 2024
8.0.33 April 25, 2023 April 2024 July 2024
8.0.34 Bug Fix July 25, 2023 July 2024 October 2024
8.0.35 Bug Fix October 25, 2023 October 2024 January 2025
8.0.36 Bug Fix January 16, 2024 January 2025 April 2025
8.0.37 Bug Fix April 2024 April 2025 July 2025

Table 5-7 MySQL 8.1 to 8.4 Release Schedule in MySQL HeatWave Service

Version General Availability (GA) date Deprecation date Unavailable date
8.1.0 Innovation July 25, 2023 October 25, 2023 January 16, 2024
8.2.0 Innovation October 25, 2023 January 16, 2024 April 16, 2024
8.3.0 Innovation January 16, 2024 April 2024 July 2024
8.4.0 LTS April 2024 April 2025 July 2025

Retrieving the Version of a MySQL Server

You can retrieve the version of the MySQL server of a DB system by using the Console, CLI, or SQL command.

You can view the MySQL version number of a DB system on the Console from the DB system details page. See Using the Console. The same information is available by running a CLI command to retrieve the DB system details. See Using the CLI. If you want to view the full MySQL version information of the DB system, you must connect to the DB system and run a SQL command.

Using a Command-Line Client

Use a command-line client such as MySQL Client or MySQL Shell to retrieve the version of a MySQL Server.

  1. Connect to the DB system using the command-line client of your choice.
  2. Run the following command:
    SELECT @@version;
You get a response similar to the following:
 SELECT @@version;
+-----------------+
| @@version       |
+-----------------+
| 8.0.34-u1-cloud |
+-----------------+
1 row in set (0.1687 sec)

8.0.34-u1-cloud is a MySQL Server version.

  • First number: Specifies the major release number such as 8.
  • Second number: Specifies the minor release number such as 0. The major and minor numbers together constitute the release series number. The series number describes the stable feature set.
  • Third number: Specifies the patch number within the release series such as 34. This is incremented for each new bug fix release.
  • u*: Specifies the MySQL HeatWave Service-specific update number such as u1. Fixes and feature development for the Oracle Cloud Infrastructure version of MySQL Server are delivered according to a different schedule to the on-premise version.
  • cloud: Specifies that this version of MySQL server was built for use in MySQL HeatWave Service only.