This page describes the extended support policy for AlloyDB for PostgreSQL.
Google Cloud offers extended support for AlloyDB for PostgreSQL major versions that reach end-of-life (EOL) based on PostgreSQL community policies. For an additional cost, AlloyDB extended support gives you the flexibility and extra time to plan your upgrades while you receive standard levels of support.
Overview
AlloyDB major versions that reach end-of-life (EOL) by the developer community are automatically enrolled in AlloyDB extended support. For more information about AlloyDB database versions and extended support timelines, see Major and minor versions supported by AlloyDB.
During extended support, AlloyDB clusters are automatically enrolled, and you receive the following benefits:
- Security fixes: instances receive patches for all critical and high severity Common Vulnerabilities and Exposures (CVE).
- Product bug fixes: resolution of bugs in AlloyDB-maintained code.
- Service Level Agreement (SLA): coverage for clusters that meet the eligibility criteria as documented in the SLA.
- Support for new cluster creation: you can create new AlloyDB clusters 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.
Clusters that are enrolled in extended support don't receive new features and service improvements that are implemented in AlloyDB for PostgreSQL after the end of your regular support period. We strongly recommend that you operate your clusters on major versions that are in regular support. To stay in regular support, you can upgrade your cluster.
Lifecycle of an extended support instance
An extended support instance goes through several phases before extended support ends.
Before the extended support period begins
Three months before a AlloyDB major version enters extended support and before billing for extended support starts, notifications for your cluster appear in the Google Cloud console. The project owner also receives email notifications about the upcoming extended support event.
Cluster enrollment
A cluster enters the extended support period when its major version reaches the AlloyDB end-of-life (EOL) date, which is three months after the major version reaches its EOL by the PostgreSQL developer community. At this time, all AlloyDB for PostgreSQL clusters running the major version that has reached EOL are automatically enrolled in extended support.
On the date when a major version enters extended support, all clusters that are running the major version are automatically enrolled and are billed for extended support, in addition to regular instance charges.
To enroll in extended support and to keep your instance on an existing major version that reaches EOL, you don't need to do anything.
End of extended support
A cluster can remain in extended support for up to three years. After a major version has been in extended support for three years, the major version is deprecated. When a major version is deprecated, AlloyDB automatically upgrades all deprecated major version clusters to the default major version.
After the upgrade, the clusters receive standard support. The upgrade is performed as part of regular AlloyDB maintenance. For more information about the end of extended support for major versions, see Deprecation.
To remove a cluster from extended support before the three-year period ends, upgrade the cluster to a major version in standard support. Whether you upgrade the cluster yourself or the cluster 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 cluster.
Pricing
Extended support is a paid service and is in addition to the current costs of your cluster.
Upgrade clusters to opt out of extended support
Although clusters are automatically enrolled in extended support, you can opt out of extended support at any time by upgrading your cluster to a major version in regular support. To avoid additional extended support charges, we recommend that you upgrade your cluster before the start of the extended support period.
If you upgrade a cluster 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 cluster, you can perform an in-place major version upgrade or you can migrate data to upgrade the database. For more information, see Upgrade a cluster's major server version.