Cloud SQL for PostgreSQL end of life dates
End-of-life and end-of-support dates for every Cloud SQL for PostgreSQL version ReleaseBytes tracks, updated nightly.
Want a warning before a version expires? Set up a free EOL alert — email or Slack, at 90, 30 and 7 days out.
| Version | Released | End of life | Status | Extended support |
|---|---|---|---|---|
| 17 | — | 1 Feb 2030 | 1296 days left | 1 Feb 2033 |
| 16 | — | 1 Feb 2029 | 931 days left | 1 Feb 2032 |
| 15 | — | 1 Feb 2028 | 565 days left | 1 Feb 2031 |
| 14 | — | 1 Feb 2027 | 200 days left | 1 Feb 2030 |
| 13 | — | 1 Feb 2026 | end of life | 1 Feb 2029 |
| 12 | — | 1 Feb 2025 | end of life | 1 Feb 2028 |
Frequently asked questions
When does Cloud SQL for PostgreSQL 17 reach end of life? ›
Cloud SQL for PostgreSQL 17 reaches end of life on 1 February 2030. Extended support ends on 1 February 2033.
When does Cloud SQL for PostgreSQL 16 reach end of life? ›
Cloud SQL for PostgreSQL 16 reaches end of life on 1 February 2029. Extended support ends on 1 February 2032.
When does Cloud SQL for PostgreSQL 15 reach end of life? ›
Cloud SQL for PostgreSQL 15 reaches end of life on 1 February 2028. Extended support ends on 1 February 2031.
When does Cloud SQL for PostgreSQL 14 reach end of life? ›
Cloud SQL for PostgreSQL 14 reaches end of life on 1 February 2027. Extended support ends on 1 February 2030.
When does Cloud SQL for PostgreSQL 13 reach end of life? ›
Cloud SQL for PostgreSQL 13 reached end of life on 1 February 2026. Extended support ends on 1 February 2029.
When does Cloud SQL for PostgreSQL 12 reach end of life? ›
Cloud SQL for PostgreSQL 12 reached end of life on 1 February 2025. Extended support ends on 1 February 2028.
Which Cloud SQL for PostgreSQL versions are still supported? ›
Currently supported Cloud SQL for PostgreSQL versions: 17, 16, 15, 14, 13, 12.
How can I get Cloud SQL for PostgreSQL end-of-life alerts? ›
ReleaseBytes sends free email or Slack alerts 90, 30 and 7 days before a tracked version reaches end of life, and its GitHub App can open an issue in your repository when something you depend on is close to EOL.