tencent cloud

TencentDB for PostgreSQL

Release Notes and Announcements
Release Notes
Product Announcements
Product Introduction
Overview
Features
Strengths
Scenarios
Information Security
Regions and AZs
Product Feature List
Large version lifecycle description
MSSQL Compatible Version
Billing
Billing Overview
Instance Type and Specification
Purchase Methods
Refund
Overdue Payments
Backup Space Billing
Database Audit Billing Overview
Getting Started
Creating TencentDB for PostgreSQL Instance
Connecting to TencentDB for PostgreSQL Instance
Managing TencentDB for PostgreSQL Instance
Importing Data
Migrating Data with DTS
Kernel Version Introduction
Kernel Version Overview
Kernel Version Release Notes
Viewing Kernel Version
Proprietary Kernel Features
Database Audit
Audit Service Description
Activating Audit Service
View Audit Logs
Modify audit services
Audit Performance Description
User Guide
Instance Management
Upgrading Instance
CPU Elastic Scaling
Read-Only Instance
Account Management
Database Management
Parameter Management
Log Management and Analysis
Backup and Restoration
Data Migration
Extension Management
Network Management
Access Management
Data Security
Tenant and Resource Isolation
Security Groups
Monitoring and Alarms
Tag
AI Practice
Using the Tencentdb_ai Plug-In to Call Large Models
Building Ai Applications with the Tencentdb Ai Plug-In
Combining Supabase to Quickly Build Backend Service Based on TencentDB for PostgreSQL
Use Cases
postgres_fdw Extension for Cross-database Access
Automatically Creating Partition in PostgreSQL
Searching in High Numbers of Tags Based on pg_roaringbitmap
Querying People Nearby with One SQL Statement
Configuring TencentDB for PostgreSQL as GitLab's External Data Source
Supporting Tiered Storage Based on cos_fdw Extension
Implement Read/Write Separation via pgpool
Implementing Slow SQL Analysis Using the Auto_explain Plugin
Using pglogical for Logical Replication
Using Debezium to Collect PostgreSQL Data
Set Up a Remote Disaster Recovery Environment for PostgreSQL Locally on CVM
Read-Only Instance and Read-Only Group Practical Tutorial
How to Use SCF for Scheduled Database Operations
Fix Table Bloat
Performance White Paper
Test Methods
Test Results
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Read-Only Instance APIs
Backup and Recovery APIs
Parameter Management APIs
Security Group APIs
Performance Optimization APIs
Account APIs
Specification APIs
Network APIs
Data Types
Error Codes
FAQs
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

ModifyDBInstanceDeployment

PDF
Focus Mode
Font Size
Last updated: 2025-08-13 17:56:33

1. API Description

Domain name for API request: postgres.intl.tencentcloudapi.com.

This API is used to modify the AZs where the nodes of a source instance reside.

A maximum of 100 requests can be initiated per second for this API.

We recommend you to use API Explorer
Try it
API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

2. Input Parameters

The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

Parameter Name Required Type Description
Action Yes String Common Params. The value used for this API: ModifyDBInstanceDeployment.
Version Yes String Common Params. The value used for this API: 2017-03-12.
Region Yes String Common Params. For more information, please see the list of regions supported by the product. This API only supports: ap-bangkok, ap-beijing, ap-chengdu, ap-chongqing, ap-guangzhou, ap-hongkong, ap-jakarta, ap-nanjing, ap-seoul, ap-shanghai, ap-shanghai-fsi, ap-shenzhen-fsi, ap-singapore, ap-tokyo, eu-frankfurt, na-ashburn, na-siliconvalley, sa-saopaulo.
DBInstanceId Yes String Instance ID.
DBNodeSet.N Yes Array of DBNode Deployment information of the instance node, which will display the information of each AZ when the instance node is deployed across multiple AZs.
The information of AZ can be obtained from the Zone field in the returned value of the DescribeZones API.
SwitchTag Yes Integer Switch time after instance configurations are modified.
  • 0: Switch immediately
  • 1: Switch at specified time
  • 2: Switch during maintenance time window

  • Default value: 0
    SwitchStartTime No String Switch start time in the format of HH:MM:SS, such as 01:00:00. When SwitchTag is 0 or 2, this parameter becomes invalid.
    SwitchEndTime No String Switch end time in the format of HH:MM:SS, such as 01:30:00. When SwitchTag is 0 or 2, this parameter becomes invalid.

    3. Output Parameters

    Parameter Name Type Description
    RequestId String The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

    4. Example

    Example1 Changing instance deployment mode to single-AZ deployment

    This example shows you how to modify the node deployment of instance "postgres-abcd1234" so that both primary and standby nodes reside in Guangzhou Zone 3.

    Input Example

    POST / HTTP/1.1
    Host: postgres.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: ModifyDBInstanceDeployment
    <Common request parameters>
    
    {
        "SwitchStartTime": "12:00:00",
        "DBNodeSet": [
            {
                "Role": "Standby",
                "Zone": "ap-guangzhou-3"
            },
            {
                "Role": "Primary",
                "Zone": "ap-guangzhou-3"
            }
        ],
        "DBInstanceId": "postgres-abcd1234",
        "SwitchTag": "1",
        "SwitchEndTime": "12:30:00"
    }
    

    Output Example

    {
        "Response": {
            "RequestId": "08fdf411-5d39-44f2-8e1d-a58ee60b237d"
        }
    }
    

    Example2 Changing instance deployment mode to multi-AZ deployment

    This example shows you how to modify the node deployment of instance "postgres-abcd1234" so that the primary node resides in Guangzhou Zone 1 and the standby node in Guangzhou Zone 7.

    Input Example

    POST / HTTP/1.1
    Host: postgres.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: ModifyDBInstanceDeployment
    <Common request parameters>
    
    {
        "SwitchStartTime": "12:00:00",
        "DBNodeSet": [
            {
                "Role": "Standby",
                "Zone": "ap-guangzhou-7"
            },
            {
                "Role": "Primary",
                "Zone": "ap-guangzhou-1"
            }
        ],
        "DBInstanceId": "postgres-abcd1234",
        "SwitchTag": "1",
        "SwitchEndTime": "12:30:00"
    }
    

    Output Example

    {
        "Response": {
            "RequestId": "08fdf411-5d39-44f2-8e1d-a58ee60b237d"
        }
    }
    

    5. Developer Resources

    SDK

    TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

    Command Line Interface

    6. Error Code

    The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

    Error Code Description
    FailedOperation.CamSigAndAuthError Authentication failed. Please try again later. If the problem persists, please contact customer service.
    FailedOperation.DatabaseAccessError Failed to access database management service. Please try again later. If the problem persists, please contact customer service.
    FailedOperation.FailedOperationError Operation failed. Please try again later.
    InternalError.InternalHttpServerError An exception occurred while executing the request.
    InvalidParameterValue.InvalidParameterValueError Incorrect parameter value
    InvalidParameterValue.InvalidZoneIdError Invalid availability zone.
    OperationDenied.CamDeniedError This operation cannot be performed.
    OperationDenied.InstanceStatusLimitError This operation cannot be performed on an instance in this status.
    OperationDenied.InstanceStatusLimitOpError This operation cannot be performed on an instance in this status.

    Help and Support

    Was this page helpful?

    Help us improve! Rate your documentation experience in 5 mins.

    Feedback