This page describes the extended support policy for Cloud SQL.
Google Cloud offers extended support for Cloud SQL for PostgreSQL major versions that reach end-of-life (EOL) by the developer community. For an additional cost, Cloud SQL extended support provides you with the flexibility and extra time to plan your upgrades while getting standard levels of support.Overview
Cloud SQL for PostgreSQL major versions that reach end-of-life (EOL) by the developer community are enrolled in Cloud SQL extended support automatically. For more information about Cloud SQL database versions and to view the timeline of when a major version enters into extended support, see Major and minor versions supported by Cloud SQL.During extended support, Cloud SQL instances are automatically enrolled and you receive the following benefits:
- Security fixes: Instances receive patches for all critical and high severity CVEs.
- Product bug fixes: Resolution of bugs in Cloud SQL-maintained code.
- Service Level Agreement (SLA) coverage: Edition-specific coverage for instances that meet the eligibility criteria as documented in the SLA.
- Support for new instance creation: You can create new Cloud SQL instances that use major versions in extended support.
When an instance is enrolled in extended support, you're charged for the cost of extended support in addition to the regular costs of the instance. For more information, see Pricing.
Instances that are enrolled in extended support don't receive the features and service improvements that are implemented in Cloud SQL after the end of your regular support period. Therefore, we strongly recommend that you operate your instances on major versions that are in regular support. To stay in regular support, you can upgrade your instance.
Lifecycle of an extended support instance
This section describes the lifecycle of an extended support instance.
Before the extended support period begins
Three months before a Cloud SQL major version enters extended support and any billing for extended support starts, notifications for your instance appear in the Google Cloud console. You also receive email notifications about the upcoming extended support event. To find which projects and instances run that major version across your organization, see View instances by version.
Instance enrollment
An instance enters extended support when its major version reaches the Cloud SQL end of life (EOL) date, which is three months after the major version reaches its EOL by the developer community. At this time, all Cloud SQL instances running the Cloud SQL for PostgreSQL major version that's EOL is enrolled in extended support automatically.
On the date when a major version enters extended support, all instances that are running the major version are enrolled automatically and are billed for extended support, in addition to regular instance charges.
To enroll in extended support and keep your instance on an existing major version that's EOL, you don't need to do anything.
End of extended support
An instance can be in extended support for three years. After a major version has reached three years in extended support, the major version is deprecated. When a major version is deprecated, Cloud SQL upgrades all deprecated major version instances to the default major version automatically. After the upgrade, the instances receive standard support. The upgrade is done as part of regular Cloud SQL maintenance. For more information about the end of extended support for major versions, see Deprecation.
To remove an instance from extended support before the three year period ends, upgrade the instance to a major version in standard support. Whether you upgrade the instance yourself or the instance is upgraded automatically, after the upgrade is complete, the additional charges for extended support are stopped, and you are billed only for the costs of the instance.
View instances by version
You can find Cloud SQL instances by major version across an organization, folder, or Google Cloud project by using the Google Cloud console or the gcloud CLI. To check which major versions are in or approaching extended support, see Major and minor versions supported by Cloud SQL.
Console
In an organization, folder, or project
To view instances 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.
-
In the Google Cloud console, go to the Database Center page.
- In the project picker in the Google Cloud console menu bar, select your organization, folder, or Google Cloud project.
- Click All Resources.
- In the Products & versions field, select the Cloud SQL major versions that you want to inspect.
- 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.
In a single project
-
In the Google Cloud console, go to the Cloud SQL Instances page.
- In the Filter field, select Type. The database versions in your project are listed.
- Select a database major version to filter the instances in your project.
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 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_IDwith--folder=FOLDER_IDor--project=PROJECT_ID.VERSION_PREFIX: the database engine or major version prefix insqladmin.googleapis.com/Instanceformat: specifyPOSTGRESto list all Cloud SQL for PostgreSQL instances, or specifyPOSTGRES_MAJOR_VERSIONwith dots replaced by underscores (for example,POSTGRES_14orPOSTGRES_17) to match a specific major version. For supported API enum strings, seeSqlDatabaseVersion.
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.
In a single project
To list Cloud SQL instances in a single project, use the
gcloud sql instances
list command:
gcloud sql instances list \
--project=PROJECT_ID \
--filter="databaseVersion:VERSION_PREFIX*"
Replace PROJECT_ID with the ID of your
Google Cloud project, and replace VERSION_PREFIX using the
same format described for organization queries.
Pricing
Extended support is a paid service and is in addition to the current costs of your instance. Pricing details for extended support are available on the Cloud SQL pricing page.
Upgrade instances to opt out of extended support
Although instances are enrolled automatically, you can opt out of extended support at any time by upgrading your instance to a major version in regular support. To avoid additional extended support charges, we recommend that you upgrade your instance before the start of the extended support period.
If you upgrade an instance that's enrolled in extended support to a major version that's in regular support, then you're no longer charged for extended support.
To upgrade your instance, you can perform an in-place major version upgrade or you can migrate data to upgrade the database. For more information, see Upgrade the database major version in-place and Upgrade the database major version by migrating data.