Database in-place major version upgrade errors

Preview — AlloyDB for PostgreSQL

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. You can process personal data for this feature as outlined in the Cloud Data Processing Addendum, subject to the obligations and restrictions described in the agreement under which you access Google Cloud. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

This document describes errors that you might encounter when you perform a database in-place major version in AlloyDB for PostgreSQL. Recommended fixes are also provided. For more information, see Troubleshoot an in-place major version upgrade.

Error: Database: database_name. extension_violation: DEPRECATED, action_required: DELETE_EXTENSION

Description: AlloyDB detects deprecated extension. The error indicates which extensions caused an error:

Database: . extension_violation: INVALID_EXTENSION_VERSION, action_required: UPGRADE_EXTENSION."+ " Query format to upgrade the extensions: ALTER EXTENSION {extension_name} UPDATE TO {target_version};. Violation list: []

Recommended fix: Delete the extension. The query format to delete an extension is DROP EXTENSION {extension_name};.

Error: Database: database_name. extension_violation: INVALID_VERSION, action_required: UPGRADE_EXTENSION

Description: AlloyDB detects invalid extension version.

Recommended fix: Upgrade the extension. The query format to upgrade an extension is ALTER EXTENSION {extension_name} UPDATE TO {target_version};.

Error: Database: database_name contains pg_largeobject

Description: AlloyDB detects pg_largeobject.

Recommended fix: Remove pg_largeobject before upgrading the AlloyDB cluster.

ERROR: out of shared memory

Description: If the instance has insufficient shared memory, you might see this error message. This error is more likely to occur if you have more than 10,000 tables.

Recommended fix: Before you start an upgrade, set the value of the max_locks_per_transaction flag to approximately twice the number of tables in the instance. The instance is restarted when you change the value of this flag.

ERROR: Insufficient connections

Description: If your instance has insufficient connection capacity, you might see this error message.

Recommended fix: We recommend that you increase the max_connections flag value by the number of databases in your instance. When you change the value of this flag, the instance is restarted.

Pre-upgrade checks are failing

Description: When you upgrade your AlloyDB cluster, your upgrade might fail due to pre-upgrade checks. Details about the violations are in the API response in the form of logs_url. You will be directed to the Google Cloud console page where the logs are present.

Recommended fix: Remove extensions.

What's next

• Troubleshoot an in-place major version upgrade.
• Learn how to perform a database in-place major version upgrade.