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
DokumentasiTencentDB for PostgreSQLUser GuideInstance ManagementModifying Instance Configuration

Modifying Instance Configuration

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-30 10:33:02
This document describes how to modify the computing specification and storage capacity of a TencentDB for PostgreSQL instance.

Overview

When the current performance or storage capacity of an instance fails to meet the demands of evolving business needs, you can perform configuration adjustments on the instance to accommodate the requirements of business growth.

Directions

1. Log in to the TencentDB for PostgreSQL console, select the target instance in the instance list, and select More > Adjust Configurations from the Operation column.
2. In the pop-up window, select the instance configuration and storage capacity you want to adjust to. The specific configuration adjustment price will be displayed below. After confirming the price, click Submit.
Note:
As the instance configuration adjustment involves instance data migration, the adjustment process will be completed with a primary/secondary switch, which will cause an instantaneous disconnection and slightly affect business access to the database instance. Therefore, we recommend you set the switch time within off-peak hours.
If you need to control the switch time, please select Specify Time in Switch Time. Then, you can select a time range. After the instance data is migrated, the system will automatically check whether it is within the switch time range, and if not, the instance will enter the Waiting for Switch status until the time falls in the time range and then complete the switch.
The time range is calculated at the granularity of one day. If the time window on the current day is missed, switch will be performed in the time window on the next day.
When the instance is in the Waiting for Switch status, you can click Switch Now in the instance list to switch immediately.

When the instance configuration is adjusted, the system checks whether the runtime values of the instance specification-related parameters exceed the upper limit of the corresponding range after the instance specification is modified. If the upper limit is exceeded, a corresponding prompt will be displayed. As shown in the figure below:

Topik sebelumnya: Setting Instance Maintenance TimeTopik selanjutnya: Setting instance availability zone for disaster recovery or region disaster recovery

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan