[[["容易理解","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-08-25 (世界標準時間)。"],[[["\u003cp\u003eThis document details potential errors encountered during an in-place major version upgrade in AlloyDB for PostgreSQL and suggests corresponding fixes.\u003c/p\u003e\n"],["\u003cp\u003eErrors related to deprecated or invalid extension versions require deleting or upgrading the extensions using specific query formats, respectively.\u003c/p\u003e\n"],["\u003cp\u003eThe presence of \u003ccode\u003epg_largeobject\u003c/code\u003e must be addressed by removing it from the AlloyDB cluster before initiating an upgrade.\u003c/p\u003e\n"],["\u003cp\u003eInsufficient shared memory or connection capacity can cause upgrade failures, requiring adjustments to the \u003ccode\u003emax_locks_per_transaction\u003c/code\u003e or \u003ccode\u003emax_connections\u003c/code\u003e flags, respectively.\u003c/p\u003e\n"],["\u003cp\u003ePre-upgrade check failures during an AlloyDB cluster upgrade are detailed in the logs, and typically require the removal of extensions to resolve.\u003c/p\u003e\n"]]],[],null,["This document describes errors that you might encounter when you perform a\ndatabase in-place major version in AlloyDB for PostgreSQL. Recommended fixes are also\nprovided. For more information, see [Troubleshoot an in-place major version upgrade](/alloydb/docs/troubleshoot/troubleshoot-database-inplace-major-version-upgrade).\n\nError: Database: database_name. extension_violation: DEPRECATED, action_required: DELETE_EXTENSION\n\n**Description:** AlloyDB detects deprecated extension. The error\nindicates which extensions caused an error: \n\n```\ndatabase_name. extension_violation: DEPRECATED_EXTENSION, action_required: DELETE_EXTENSION.\"+\" Query format to delete the extensions: `DROP EXTENSION {extension_name}; Violation list: [extensions]\n```\n\n**Recommended fix:** Delete the extension. The query format to delete an\nextension is `DROP EXTENSION {extension_name};`.\n\nError: Database: database_name. extension_violation: INVALID_EXTENSION_VERSION, action_required: UPGRADE_EXTENSION\n\n**Description:** AlloyDB detects invalid extension version.\n\n**Recommended fix:** Upgrade the extension. The query format to upgrade an\nextension is `ALTER EXTENSION {extension_name} UPDATE TO {target_version};`.\n\nError: Database: database_name contains pg_largeobject\n\n**Description:** AlloyDB detects `pg_largeobject`.\n\n**Recommended fix:** Remove `pg_largeobject` before upgrading the\nAlloyDB cluster.\n\nERROR: out of shared memory\n\n**Description:** If the instance has insufficient shared memory, you might see\nthis error message. This error is more likely to occur if you have more than\n10,000 tables.\n\n**Recommended fix:** Before you start an upgrade, set the value of the\n[`max_locks_per_transaction`](/alloydb/docs/reference/database-flags#postgres-m)\nflag to approximately twice the number of tables in the instance. The instance\nis restarted when you change the value of this flag.\n\nERROR: Insufficient connections\n\n**Description:** If your instance has insufficient connection capacity, you\nmight see this error message.\n\n**Recommended fix:** We recommend that you increase the\n[`max_connections`](/alloydb/docs/reference/database-flags#postgres-m)\nflag value by the number of databases in your instance. When you change the\nvalue of this flag, the instance is restarted.\n\nPre-upgrade checks are failing\n\n**Description:** When you upgrade your AlloyDB cluster, your\nupgrade might fail due to pre-upgrade checks. Details about the violations are\nin the API response in the form of `logs_url`. You are directed to\nthe Google Cloud console page where the logs are present.\n\n**Recommended fix:** Based on the error message, see other errors listed earlier in this document to resolve the specific issue.\n\nWhat's next\n\n- [Troubleshoot an in-place major version upgrade](/alloydb/docs/troubleshoot/troubleshoot-database-inplace-major-version-upgrade).\n- Learn how to [perform a database in-place major version upgrade](/alloydb/docs/upgrade-db-inplace-major-version)."]]
