Database 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.

Major version Minor version Regular support start date Extended support start date Deprecation date
MySQL 9.79.7.2 August 6, 2026 Not applicable Not applicable
MySQL 8.4 (default)8.4.11 October 1, 2024 Not applicable Not applicable
MySQL 8.08.0.46 (default)
8.0.45
8.0.44
8.0.43
8.0.42
8.0.41
8.0.40
8.0.39
8.0.37
8.0.36
8.0.35
8.0.34
8.0.33
8.0.32
8.0.31
8.0.30
8.0.28
8.0.27
8.0.26
8.0.18
August 30, 2020 January 1, 2027 July 1, 2029
Major version Minor version Regular support start date Extended support start date Deprecation date
PostgreSQL 18 (default) 18.6 September 25, 2025 - -
PostgreSQL 17 17.11 October 22, 2024 February 1, 2030 February 1, 2033
PostgreSQL 1616.15 June 7, 2024February 1, 2029February 1, 2032
PostgreSQL 1515.19 May 24, 2023 February 1, 2028 February 1, 2031
PostgreSQL 14 14.24 November 11, 2021 February 1, 2027 February 1, 2030
PostgreSQL 1313.23 November 5, 2020 February 1, 2026 February 1, 2029
PostgreSQL 1212.22 May 21, 2020 February 1, 2025* February 1, 2028
* 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.

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.

For PostgreSQL 9.6, the first two numbers in the version number form the major version, and the last number is the minor version. For example, for version 9.6.1, Cloud SQL uses 9.6 as the major version, and 1 as the minor version. For PostgreSQL 10 and later, the first number is the major version. For example, for version 10.1, 10 is the major version, and 1 is 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.

You can check the database version of a single Cloud SQL instance or find instances by version across a Cloud de Confiance project, folder, or organization by using the Cloud de Confiance console or the gcloud CLI.

Console

For a single instance

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

    Go to Cloud SQL Instances

  2. To open the Overview page of an instance, click the instance name.
  3. In the Configuration card, view the Database version.

In a single project

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

    Go to Cloud SQL Instances

  2. In the Filter field, select Type. The database versions in your project are listed.
  3. Select a database version to filter the instances in your project.

In an organization, folder, or project

To view Cloud SQL instances and their database versions across an organization or folder in Database Center, make sure that you have the Database Center Viewer (roles/databasecenter.viewer) Identity and Access Management (IAM) role on that organization or folder. For more information, see Set up Database Center.

  1. In the Cloud de Confiance console, go to the Database Center page.

    Go to Database Center

  2. In the project picker in the Cloud de Confiance console menu bar, select your organization, folder, or Cloud de Confiance project.
  3. Click All Resources, and then use the Products & versions filter to select the Cloud SQL versions that you want to inspect.
  4. Optional: To download the filtered fleet inventory to a CSV file, click CSV Export. For more information, see Filter resources and export fleet inventory information.

gcloud

For information about installing and getting started with the gcloud CLI, see Install the gcloud CLI. For information about starting Cloud Shell, see Use Cloud Shell.

In a single project

To list Cloud SQL instances and their database versions in a single project, use the gcloud sql instances list command:

gcloud sql instances list --project=PROJECT_ID

Replace PROJECT_ID with the ID of your Cloud de Confiance project. To filter by engine or major version, add --filter="databaseVersion:VERSION_PREFIX*", where VERSION_PREFIX is an API enum prefix such as MYSQL_8_4 or POSTGRES_17.

In an organization, folder, or project

To list Cloud SQL instances across an organization or folder by using gcloud asset list, make sure that the Cloud Asset Inventory API is enabled on your quota project and that you have the Cloud Asset Viewer (roles/cloudasset.viewer) IAM role on the organization, folder, or project. For more information, see Roles and permissions.

gcloud asset list \
    --organization=ORGANIZATION_ID \
    --asset-types="sqladmin.googleapis.com/Instance" \
    --content-type=resource \
    --filter="resource.data.databaseVersion:VERSION_PREFIX*" \
    --format="table(
        resource.data.project,
        resource.data.name,
        resource.data.databaseVersion,
        resource.data.state,
        resource.data.settings.activationPolicy,
        resource.data.region
    )"

Replace the following:

  • ORGANIZATION_ID: the numeric ID of your organization. To query a folder or a single project instead, replace --organization=ORGANIZATION_ID with --folder=FOLDER_ID or --project=PROJECT_ID.
  • VERSION_PREFIX: the database engine or major version prefix in sqladmin.googleapis.com/Instance format: specify MYSQL or POSTGRES to list all instances for that database engine, or append the major version with dots replaced by underscores (for example, MYSQL_8_4 or POSTGRES_17) to match a specific major version.

The output includes both running instances (activationPolicy: ALWAYS) and stopped instances (activationPolicy: NEVER), along with the project ID, instance name, full database version, state, and region.

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 and Cloud SQL for PostgreSQL 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 and Cloud SQL for PostgreSQL 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.

By default, when you create a MySQL 8.0 instance without specifying a minor version, the instance is enabled for automatic minor version upgrade. If your Cloud SQL for MySQL instance is running version 8.0.35 or later, then you can configure the instance to enable automatic minor version upgrade.

When automatic minor version upgrade is enabled for your instance, 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. The upgrades occur only during scheduled maintenance events and not during self-service maintenance.

If your instance is running Cloud SQL for MySQL version 8.0.34 or earlier, then you must upgrade the minor version of Cloud SQL for MySQL 8.0 to a later minor version manually. For more information, see Upgrade the database minor version. After you upgrade your instance manually to Cloud SQL for MySQL version 8.0.35 or later, then you can enable automatic minor version upgrade.