对于 Cloud SQL for MySQL 主要版本,项目所有者会在延长支持的第二年结束时收到弃用通知。
次要版本支持
Cloud SQL 会在数据库引擎开发者社区正式发布后的三个月内支持新的次要版本。Cloud SQL 支持新的次要版本后,会自动在新版本上预配新实例。在下一次计划内维护发布期间,Cloud SQL 会将现有实例升级到新版本。
Cloud SQL for MySQL 8.0 是此政策的例外情况,它会在默认的次要版本上预配新实例。如需了解详情,请参阅 MySQL 8.0。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Database versions and version policies\n\n\u003cbr /\u003e\n\nMySQL \\| [PostgreSQL](/sql/docs/postgres/db-versions \"View this page for the PostgreSQL database engine\") \\| [SQL Server](/sql/docs/sqlserver/db-versions \"View this page for the SQL Server database engine\")\n\n\u003cbr /\u003e\n\nThis page describes Cloud SQL's database version support policies.\n| **Important:** All Cloud SQL instances that are running community end-of-life (EOL) major versions of MySQL 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](/sql/docs/mysql/extended-support#pricing).\n\nDatabase versions supported by Cloud SQL\n----------------------------------------\n\nThe database engines supported by Cloud SQL include multiple versions.\nThe versions can vary in capabilities and in the types of issues that\narise. While performing an upgrade can impact your users,\nproviding up-to-date database features and important patches is also critical.\nCloud SQL keeps your instances up-to-date with patches and\nminor version updates automatically.\n\nMajor and minor versions supported by Cloud SQL\n-----------------------------------------------\n\nCloud SQL supports the following database versions.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\\* 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.\n\n\u003cbr /\u003e\n\nTo avoid additional charges for extended support, we recommend that you\n[upgrade your instance](/sql/docs/mysql/upgrade-major-db-version-inplace) before May 1, 2025.\n\n\nCloud SQL database version format\n---------------------------------\n\nFor MySQL, the first two numbers in the version number form the major version, and\nthe last number is the minor version.\nFor example, for **version 5.7.13** , Cloud SQL uses **5.7** as the major version,\nand **13** as the minor version.\n\n\u003cbr /\u003e\n\n| **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.\n\n### How to identify the database version of your Cloud SQL instance\n\nYou specify the database version when you create a Cloud SQL instance.\nIf you don't specify a database version, then Cloud SQL uses the default\ndatabase version.\n\nTo view the database version of a Cloud SQL instance, do the following:\n\n1. In the Google Cloud console, go to the **Cloud SQL Instances** page.\n\n [Go to Cloud SQL Instances](https://console.cloud.google.com/sql)\n2. To open the **Overview** page of an instance, click the instance name.\n3. In the **Configuration** card, view the **Database version**.\n\nTo filter instances by a specific database version within your Cloud SQL project, do the following:\n\n1. In the Google Cloud console, go to the **Cloud SQL Instances** page.\n\n [Go to Cloud SQL Instances](https://console.cloud.google.com/sql)\n2. In the **Filter** field, select **Type**. The database versions that are within your project are listed.\n3. To filter the instances, select a database version within your project.\n\nTo view all Cloud SQL instances and their database versions in your organization,\nuse [Database Center](/database-center/docs/overview).\nYou can also switch views in Database Center from project\nto folders or organizations to get a complete list of all your\nCloud SQL instances.\nFor more information, see\n[Filter resources and export fleet inventory information](/database-center/docs/filter-resources-export-fleet-inventory-information).\n\nMajor version lifecycle\n-----------------------\n\nThis section describes the support lifecycle for major versions in Cloud SQL.\n\n### Regular support\n\nCloud 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.\n\n\u003cbr /\u003e\n\n### Extended support\n\nFor Cloud SQL for MySQL\nmajor versions that have\nreached their EOL, Cloud SQL offers extended\nsupport. Extended support lets you continue running your Cloud SQL\ninstances for three years even after the developer community stops supporting\nthe major versions on which the instances are running. Extended support\nis offered for three years.\nYou can use this time to plan, test, and perform the upgrade of your instances\nto a major version that is in regular support. For more information about\nperforming a major version upgrade, see\n[Upgrade the database major version in-place](/sql/docs/mysql/upgrade-major-db-version-inplace)\nand [Upgrade the database major version by migrating data](/sql/docs/mysql/upgrade-major-db-version-migrate).\n\nFor more information about\nextended support, see [Extended support in Cloud SQL](/sql/docs/mysql/extended-support).\n\n### Deprecation\n\nAfter extended support has ended for a specific major version, Cloud SQL\ndeprecates the major version. An instance running on a deprecated major version is\nupgraded to the default major and minor version for the database engine\nautomatically. Cloud SQL sends a deprecation notice to project\nowners at least 12 months before the deprecation date.\n\nFor Cloud SQL for MySQL\nmajor versions, project owners receive a deprecation notice\nat the end of the second year of extended support.\n\nMinor version support\n---------------------\n\nCloud 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. For more information, see [MySQL 8.0](#mysql-8.0).\n\n\u003cbr /\u003e\n\nCloud SQL determines the target minor version for each database engine.\nWhen the target minor version is different from the minor version for a\nCloud SQL instance, Cloud SQL upgrades that version during\nthe next maintenance cycle. You can control the day and time when maintenance\nrestarts occur by\n[setting a maintenance window](/sql/docs/mysql/set-maintenance-window)\nfor your instance.\n\n### MySQL 8.0\n\nCloud SQL for MySQL 8.0 provisions instances on a default minor version, which might\nnot be the latest minor version.\n\nAfter Cloud SQL for MySQL supports a new minor version, you can\n[upgrade existing Cloud SQL for MySQL instances](/sql/docs/mysql/upgrade-minor-db-version)\nto the new minor version. After the minor version\nbecomes the default version, then Cloud SQL provisions new instances\non the new minor version automatically.\n| **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."]]