Database versions and version policies

This page describes Cloud SQL's database version support policies.

Database versions supported by Cloud SQL

The database engines supported by Cloud SQL include multiple versions. The versions can vary in capabilities and in the types of issues that arise. While performing an upgrade can impact your users, providing up-to-date database features and important patches is also critical. Cloud SQL keeps your instances up-to-date with patches and minor version updates automatically.

Major and minor versions supported by Cloud SQL

Cloud SQL supports the following database versions.

* From February 1, 2025 through April 30, 2025, Google has waived charges for extended support. Starting on May 1, 2025, all instances running on major versions that have reached end of life (EOL) will be charged for extended support.

To avoid additional charges for extended support, we recommend that you upgrade your instance before May 1, 2025.

Cloud SQL database version format

For MySQL, the first two numbers in the version number form the major version, and the last number is the minor version. For example, for version 5.7.13 , Cloud SQL uses 5.7 as the major version, and 13 as the minor version.

How to identify the database version of your Cloud SQL instance

You specify the database version when you create a Cloud SQL instance. If you don't specify a database version, then Cloud SQL uses the default database version.

To view the database version of a Cloud SQL instance, do the following:

1. In the Google Cloud console, go to the Cloud SQL Instances page.

   Go to Cloud SQL Instances

2. To open the Overviewpage of an instance, click the instance name.
3. In the Configurationcard, view the Database version.

To filter instances by a specific database version within your Cloud SQL project, do the following:

1. In the Google Cloud console, go to the Cloud SQL Instances page.

   Go to Cloud SQL Instances

2. In the Filterfield, select Type. The database versions that are within your project are listed.
3. To filter the instances, select a database version within your project.

To view all Cloud SQL instances and their database versions in your organization, use Database Center . You can also switch views in Database Center from project to folders or organizations to get a complete list of all your Cloud SQL instances. For more information, see Filter resources and export fleet inventory information .

Major version lifecycle

This section describes the support lifecycle for major versions in Cloud SQL.

Regular support

Cloud SQL supports new major versions within five months of their general availability release by the database engine developer community. The first phase of this support is regular support. During regular support, Cloud SQL provides minor version and maintenance updates for the database engine. Cloud SQL also applies security fixes to the instances. Cloud SQL offers regular support for a major version as long as the database engine developer community supports the major version. After the major version reaches end-of-life (EOL) by the community, the major version enters extended support in Cloud SQL.

Extended support

For Cloud SQL for MySQL major versions that have reached their EOL, Cloud SQL offers extended support. Extended support lets you continue running your Cloud SQL instances for three years even after the developer community stops supporting the major versions on which the instances are running. Extended support is offered for three years. You can use this time to plan, test, and perform the upgrade of your instances to a major version that is in regular support. For more information about performing a major version upgrade, see Upgrade the database major version in-place and Upgrade the database major version by migrating data .

For more information about extended support, see Extended support in Cloud SQL .

Deprecation

After extended support has ended for a specific major version, Cloud SQL deprecates the major version. An instance running on a deprecated major version is upgraded to the default major and minor version for the database engine automatically. Cloud SQL sends a deprecation notice to project owners at least 12 months before the deprecation date.

For Cloud SQL for MySQL major versions, project owners receive a deprecation notice at the end of the second year of extended support.

Minor version support

Cloud SQL supports new minor versions within three months of their general availability release by the database engine developer community. After Cloud SQL supports a new minor version, Cloud SQL provisions new instances on the new version automatically. During the next scheduled maintenance rollout, Cloud SQL upgrades existing instances to the new version. An exception to this policy is Cloud SQL for MySQL 8.0, which provisions new instances on the default minor version and only upgrades the minor versions of instances that are enabled for automatic minor version upgrade . For more information, see MySQL 8.0 .

Cloud SQL determines the target minor version for each database engine. When the target minor version is different from the minor version for a Cloud SQL instance, Cloud SQL upgrades that version during the next maintenance cycle. You can control the day and time when maintenance restarts occur by setting a maintenance window for your instance.

MySQL 8.0

Cloud SQL provisions MySQL 8.0 instances on the default minor version, which is one minor version earlier than the latest minor version.

Cloud SQL supports the automatic minor version upgrade of Cloud SQL for MySQL 8.0 instances that are running MySQL version 8.0.35 or later.

When you create a MySQL 8.0 instance without specifying a minor version, the instance is enabled for automatic minor version upgrade.

If automatic minor version upgrade is enabled, then your Cloud SQL for MySQL instance is upgraded automatically to the default minor version of Cloud SQL for MySQL 8.0 during its regular scheduled maintenance update . Automatic minor version upgrade occurs only during scheduled maintenance events and not during self-service maintenance.