All Products
Search
Document Center

AnalyticDB:ModifyMasterSpec

Last Updated:Nov 05, 2025

Changes the specifications of coordinator node resources for an AnalyticDB for PostgreSQL instance.

Operation description

This operation is not available for instances in reserved storage mode.

Before you call this operation, make sure that you are familiar with the billing of AnalyticDB for PostgreSQL. For more information, see Billing methods and AnalyticDB for PostgreSQL pricing.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
gpdb:ModifyMasterSpecupdate
*DBInstance
acs:gpdb:*:{#accountId}:dbinstance/{#DBInstanceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ResourceGroupIdstringNo

The ID of the resource group to which the instance belongs. For information about how to obtain the ID of a resource group, see View basic information of a resource group.

rg-bp67acfmxazb4p****
DBInstanceIdstringYes

The instance ID.

Note You can call the DescribeDBInstances operation to query the IDs of all AnalyticDB for PostgreSQL instances in a region.
gp-xxxxxxxxx
DBInstanceDescriptionstringNo

The description of the instance.

test
MasterCUintegerNo

The specifications of coordinator node resources. Valid values:

  • 2 CU
  • 4 CU
  • 8 CU
  • 16 CU
  • 32 CU
Note You are charged for coordinator node resources of more than 8 compute units (CUs).
8 CU
MasterAISpecstringNo

This parameter must be specified if you want to change coordinator nodes to AI coordinator nodes.

Note
  • You cannot specify the MasterAISpec and MasterCU parameters at the same time.
  • You can change coordinator nodes to AI coordinator nodes only in specific regions and zones.
  • Only AnalyticDB for PostgreSQL V7.0 instances of Basic Edition support AI coordinator nodes.
  • You can view the valid values of this parameter on the configuration change page of coordinator nodes.
  • ADB.AIMedium.2

    Response parameters

    ParameterTypeDescriptionExample
    object
    RequestIdstring

    The request ID.

    ABB39CC3-4488-4857-905D-2E4A051D0521
    ErrorMessagestring

    The returned message.

    This parameter is returned only if the request fails.

    ******
    DbInstanceIdstring

    The instance ID.

    gp-bp12ga6v69h86****
    Statusboolean

    Indicates whether the request was successful. Valid values:

    • false
    • true
    true

    Examples

    Sample success responses

    JSONformat

    {
      "RequestId": "ABB39CC3-4488-4857-905D-2E4A051D0521",
      "ErrorMessage": "******",
      "DbInstanceId": "gp-bp12ga6v69h86****",
      "Status": true
    }

    Error codes

    For a list of error codes, visit the Service error codes.

    Change history

    Change timeSummary of changesOperation
    2024-08-29The internal configuration of the API is changed, but the call is not affectedView Change Details