Google Cloud は、デベロッパー コミュニティによってサポートが終了した(EOL の)Cloud SQL for MySQL のメジャー バージョンに対して拡張サポートを提供しています。追加料金で利用できる Cloud SQL 拡張サポートでは、標準レベルのサポートを受けながら、アップグレードを計画するための柔軟性と余裕のある時間を確保できます。
概要
デベロッパー コミュニティによってサポートが終了した(EOL の)Cloud SQL for MySQL のメジャー バージョンは、Cloud SQL の拡張サポートに自動的に登録されます。Cloud SQL データベース バージョンの詳細と、メジャー バージョンが拡張サポートに移行するまでのタイムラインについては、Cloud SQL でサポートされているメジャー バージョンとマイナー バージョンをご覧ください。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["# Extended support for Cloud SQL\n\n\u003cbr /\u003e\n\nMySQL \\| [PostgreSQL](/sql/docs/postgres/extended-support \"View this page for the PostgreSQL database engine\") \\| SQL Server\n\n\u003cbr /\u003e\n\nThis page describes the extended support policy for Cloud SQL.\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](#pricing).\nGoogle Cloud offers extended support for Cloud SQL for MySQL 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.\n\n\u003cbr /\u003e\n\nOverview\n--------\n\nCloud SQL for MySQL 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](/sql/docs/mysql/db-versions#database-version-support).\n\nDuring extended support, Cloud SQL instances are automatically enrolled and\nyou receive the following benefits:\n\n- **Security fixes**: Instances receive patches for all critical and high severity CVEs.\n- **Product bug fixes**: Resolution of bugs in Cloud SQL-maintained code.\n- **Service Level Agreement (SLA) coverage** : Edition-specific coverage for instances that meet the eligibility criteria as documented in the [SLA](/sql/sla).\n- **Support for new instance creation**: You can create new Cloud SQL instances that use major versions in extended support.\n\nWhen an instance is enrolled in extended support, you're charged\nfor the cost of extended support in addition to the regular costs of the instance.\nFor more information, see [Pricing](#pricing).\n\nInstances that are enrolled in extended support\ndon't receive the features and service improvements that are\nimplemented in Cloud SQL after the end of your regular support period.\nTherefore, we strongly recommend that you operate your instances on major versions\nthat are in regular support. To stay in regular support,\nyou can [upgrade your instance](#opt-out).\n\nLifecycle of an extended support instance\n-----------------------------------------\n\nThis section describes the lifecycle of an extended support instance.\n\n### Before the extended support period begins\n\nThree months before a Cloud SQL major version enters extended support\nand any billing for extended support starts,\nnotifications for your instance appear in the Google Cloud console.\nYou also receive email notifications about the upcoming extended support event.\n\n### Instance enrollment\n\nAn instance enters extended support when its major version reaches the\nCloud SQL end of life (EOL) date, which is three months after\nthe major version reaches its EOL by the developer community.\nAt this time, all Cloud SQL instances running the\nCloud SQL for MySQL major version that's EOL is\nenrolled in extended support automatically.\n| **Note:** Some major versions, such as MySQL 5.6 , start extended support later than three months after their community EOL date. To view the extended support start date for each major version, see [Major and minor versions supported by Cloud SQL](/sql/docs/mysql/db-versions#database-version-support).\n\nOn the date when a major version enters extended support, all instances that are\nrunning the major version are enrolled automatically\nand are billed for extended support, in addition to regular instance charges.\n\nTo enroll in extended support and keep your instance on an existing major\nversion that's EOL, you don't need to do anything.\n\n### End of extended support\n\nAn instance can be in extended support for three years.\nAfter a major version has reached three years in extended support, the major version\nis deprecated. When a major version is deprecated, Cloud SQL\nupgrades all deprecated major version instances to\nthe default major version automatically. After the upgrade,\nthe instances receive standard support.\nThe upgrade is done as part of regular Cloud SQL maintenance. For more\ninformation about the end of extended support for major versions,\nsee [Deprecation](/sql/docs/mysql/db-versions#deprecation).\n\nTo remove an instance from extended support before the three year period ends, [upgrade the instance](#opt-out) to a major version in standard support.\nWhether you upgrade the instance yourself or the instance is upgraded automatically,\nafter the upgrade is complete, the additional charges for extended support are\nstopped, and you are billed only for the costs of the instance.\n\nView instances in extended support\n----------------------------------\n\nTo view a list of extended support instances in a 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 view a filtered list of instances, enter a major version in extended support.\n\nTo view a list of extended support instances in an organization, do the following:\n\n1. In the Google Cloud console, go to the **Database Center** page.\n\n [Go to Database Center](https://console.cloud.google.com/database-center)\n2. From the drop-down in the Google Cloud console menu bar, select\n your organization.\n\n3. Click **All Resources**.\n\n4. In the **Products \\& versions** field, select the Cloud SQL major\n versions that are in extended support.\n\nPricing\n-------\n\nExtended support is a paid service and is in addition to the current\ncosts of your instance. Pricing details for extended support are available on\nthe [Cloud SQL pricing page](/sql/pricing#extended-support-pricing).\n| **Important:** 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. To avoid additional charges for extended support, we recommend that you [upgrade your instance](/sql/docs/mysql/upgrade-major-db-version-inplace) before May 1, 2025.\n\nUpgrade instances to opt out of extended support\n------------------------------------------------\n\nAlthough instances are enrolled automatically, you can opt out\nof extended support at any time by upgrading your\ninstance to a major version in regular support. To avoid additional extended support\ncharges, we recommend that you upgrade your instance before the start of\nthe extended support period.\n\nIf you upgrade an instance that's enrolled in extended support to a major version\nthat's in regular support, then you're no longer charged for extended support.\n\nTo upgrade your instance, you can perform an\nin-place major version upgrade or you can migrate data to upgrade the database.\nFor more information, 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)."]]