Time to Bail · Boarding pass
Act. You can stay.
From February 1, 2027, PostgreSQL 14 instances pay $0.07 per vCPU per hour extra. Upgrade to stop the fee.[1]
Act means: change a setting or plan before the date. You can stay.
Cloud SQL for PostgreSQL 14 costs extra from February 1, 2027
Cloud SQL moves PostgreSQL 14 into paid extended support on February 1, 2027. The fee is added per vCPU per hour, and it grows in the third year.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
In the console, open Cloud SQL and check the database version of each instance and replica.
Make a clone, upgrade it and run your app against it first.
Upgrade PostgreSQL 14 instances before February 1, 2027.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| Paid extended support starts | February 1, 2027[1] |
|---|---|
| Version | PostgreSQL 14[1] |
| Who is enrolled | All instances on end-of-life MySQL and PostgreSQL major versions[1] |
| Extended support ends | February 1, 2030[1] |
| After that | Cloud SQL upgrades the instance to the default major and minor version[1] |
| Extra fee in the first two years (Iowa) | $0.07 per vCPU per hour[2] |
| Extra fee from the third year (Iowa) | $0.14 per vCPU per hour[2] |
| High availability vCPUs, first two years | $0.14 per vCPU per hour[2] |
| Committed use discounts | Do not apply to extended support prices[2] |
| Read replicas | Charged at the same rate as stand-alone instances[2] |
| How to stop the fee | Upgrade the instance to a major version in standard support[3] |
| Instances still on PostgreSQL 14 | Pay the extra fee from February 1, 2027[1] |
Check it yourself. Every fact above links here.
Time to bail on Cloud SQL for PostgreSQL 14? Act. You can stay. From February 1, 2027, PostgreSQL 14 instances pay $0.07 per vCPU per hour extra. Upgrade to stop the fee.
On our scale this is Act: change a setting or plan before the date. You can stay.
Cloud SQL moves PostgreSQL 14 into paid extended support on February 1, 2027. The fee is added per vCPU per hour, and it grows in the third year.
Here are the facts we checked:
You can stay on Cloud SQL. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Google Cloud is the main source for this page. Cloud SQL has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Instances still on PostgreSQL 14: Pay the extra fee from February 1, 2027.
The date to remember is February 1, 2027. Make the change before then.
A few tips:
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on Cloud SQL for PostgreSQL 14 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.