This page describes Cloud SQL's database version support policies.
> [!IMPORTANT]
> **Important:** All Cloud SQL instances that are running community end-of-life (EOL) major versions of MySQL and PostgreSQL are enrolled in extended support. If your instance is running an EOL major version, then you will be charged for extended support starting on May 1, 2025. For more information about extended support pricing, see [Pricing](https://docs.cloud.google.com/sql/docs/mysql/extended-support#pricing).
## 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 8.4 (default) | 8.4.10 | October 1, 2024 | --- | --- |
| MySQL 8.0 | 8.0.46 8.0.45 (default) 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 |
| MySQL 5.7 | 5.7.44 | August 1, 2016 | February 1, 2025\* | February 1, 2028 |
| MySQL 5.6 | 5.6.51 | August 1, 2016 | February 1, 2025\* | February 1, 2028 |
| Major version | Minor version | Regular support start date | Extended support start date | Deprecation date |
|---|---|---|---|---|
| PostgreSQL 18 (default) | 18.4 | September 25, 2025 | - | - |
| PostgreSQL 17 | 17.10 | October 22, 2024 | February 1, 2030 | February 1, 2033 |
| PostgreSQL 16 | 16.14 | June 7, 2024 | February 1, 2029 | February 1, 2032 |
| PostgreSQL 15 | 15.18 | May 24, 2023 | February 1, 2028 | February 1, 2031 |
| PostgreSQL 14 | 14.23 | November 11, 2021 | February 1, 2027 | February 1, 2030 |
| PostgreSQL 13 | 13.23 | November 5, 2020 | February 1, 2026 | February 1, 2029 |
| PostgreSQL 12 | 12.22 | May 21, 2020 | February 1, 2025\* | February 1, 2028 |
| PostgreSQL 11 | 11.22 | September 27, 2019 | February 1, 2025\* | February 1, 2028 |
| PostgreSQL 10 | 10.23 | March 27, 2020 | February 1, 2025\* | February 1, 2028 |
| PostgreSQL 9.6 | 9.6.24 | April 1, 2018 | February 1, 2025\* | February 1, 2028 |
The mainstream end date and the Microsoft extended support end dates follow the
[Microsoft SQL Server support lifecycle](https://learn.microsoft.com/en-us/lifecycle/products/).
These dates are different than the Cloud SQL extended support dates
that apply to Cloud SQL for PostgreSQL and Cloud SQL for MySQL.
While Cloud SQL does charge for extended support for MySQL and
PostgreSQL, Cloud SQL doesn't charge for extended support
for Microsoft SQL Server.
| Major version | Minor version | Support start date | Mainstream support end date | Extended support end date |
|---|---|---|---|---|
| SQL Server 2025 Standard | CU2 | November 18, 2025 | [January 6, 2031](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2025) | January 6, 2036 |
| SQL Server 2025 Enterprise | CU2 | November 18, 2025 | [January 6, 2031](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2025) | January 6, 2036 |
| SQL Server 2025 Express | CU2 | November 18, 2025 | [January 6, 2031](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2025) | January 6, 2036 |
| SQL Server 2022 Standard | CU19 | June 26, 2023 | [January 11, 2028](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2022) | January 11, 2033 |
| SQL Server 2022 Enterprise | CU19 | June 26, 2023 | [January 11, 2028](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2022) | January 11, 2033 |
| SQL Server 2022 Express | CU19 | June 26, 2023 | [January 11, 2028](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2022) | January 11, 2033 |
| SQL Server 2022 Web | CU19 | June 26, 2023 | [January 11, 2028](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2022) | January 11, 2033 |
| SQL Server 2019 Standard | CU32 | June 24, 2021 | [February 28, 2025](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2019) | January 8, 2030 |
| SQL Server 2019 Enterprise | CU32 | June 24, 2021 | [February 28, 2025](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2019) | January 8, 2030 |
| SQL Server 2019 Express | CU32 | June 24, 2021 | [February 28, 2025](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2019) | January 8, 2030 |
| SQL Server 2019 Web | CU32 | June 24, 2021 | [February 28, 2025](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2019) | January 8, 2030 |
| SQL Server 2017 Standard | CU31 | February 19, 2020 | [October 11, 2022](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017) | October 12, 2027 |
| SQL Server 2017 Enterprise | CU31 | February 19, 2020 | [October 11, 2022](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017) | October 12, 2027 |
| SQL Server 2017 Express | CU31 | February 19, 2020 | [October 11, 2022](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017) | October 12, 2027 |
| SQL Server 2017 Web | CU31 | February 19, 2020 | [October 11, 2022](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017) | October 12, 2027 |
\* 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](https://docs.cloud.google.com/sql/docs/mysql/upgrade-major-db-version-inplace) 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.
> [!NOTE]
> **Note:** Cloud SQL's version terminology differs from MySQL's terminology. In MySQL documentation, the major version is referred to as the release series number and the minor version is referred to as the release series 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.
For SQL Server, the year provides the major version number and the minor version
is the supported Cumulative Update (CU). For example,
for SQL Server 2022 Enterprise CU11, **2022 Enterprise** is the major version number
and **CU11** is the minor version number.
### 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](https://console.cloud.google.com/sql)
2. To open the **Overview** page of an instance, click the instance name.
3. In the **Configuration** card, 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](https://console.cloud.google.com/sql)
2. In the **Filter** field, 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](https://docs.cloud.google.com/database-center/docs/overview).
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](https://docs.cloud.google.com/database-center/docs/filter-resources-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 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](https://docs.cloud.google.com/sql/docs/mysql/upgrade-major-db-version-inplace)
and [Upgrade the database major version by migrating data](https://docs.cloud.google.com/sql/docs/mysql/upgrade-major-db-version-migrate).
For more information about
extended support, see [Extended support in Cloud SQL](https://docs.cloud.google.com/sql/docs/mysql/extended-support).
### 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](https://docs.cloud.google.com/sql/docs/mysql/upgrade-minor-db-version#auto-upgrade). For more information, see [MySQL 8.0](https://docs.cloud.google.com/sql/docs/db-versions#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](https://docs.cloud.google.com/sql/docs/mysql/set-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](https://docs.cloud.google.com/sql/docs/mysql/upgrade-minor-db-version#auto-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](https://docs.cloud.google.com/sql/docs/mysql/upgrade-minor-db-version#enable-auto-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](https://docs.cloud.google.com/sql/docs/mysql/maintenance). 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](https://docs.cloud.google.com/sql/docs/mysql/upgrade-minor-db-version#manual-upgrade). 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.
> [!NOTE]
> **Note:** Cloud SQL might not support each new minor version released by the database engine developer. For example, Cloud SQL might not support a minor version that's found not to work well with Cloud SQL.