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
ドキュメントTencentDB for PostgreSQLBillingInstance Type and Specification

Instance Type and Specification

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-04-30 12:16:03
A database instance is a standalone database environment that runs in the Tencent Cloud. It can contain multiple databases created by users and can be accessed by using the same tools and applications as those for a standalone database instance.

Instance Types

TencentDB for PostgreSQL supports the following types of instances:
Instance Type
Description
Architecture
Visible in the Instance List
Capability
Primary instance
An instance that can be read from and written to
High-availability edition
Yes
The primary instance can associate with read-only instances to realize read/write separation.
Read-only instance
An instance that can only be read from
Single-node read-only
Yes
A read-only instance cannot exist on its own. It must instead be associated with a source instance, with its data only being synced from the source instance. It must also reside in the same region as the source instance. By default, up to six read-only instances can be created for a primary instance.

Reference documents

For more information on the creation of the read-only instance and relevant notes, see Read-Only Instance Overview.
For more information on how to create and configure an RO group, see Managing RO Groups.
Note:
When the used capacity of the instance exceeds the purchased capacity, the database instance will be locked and become read-only. You can set alarms for capacity usage.

Supported Instance Specifications

Edition
Version
Specification Type
CPU and Memory
Disk Capacity
Maximum Number of Connections
Dual-machine high availability (one primary and one secondary) instance, read-only instance
11,12,13,14,15,16,17
General - local high-performance SSD
1core 2GiB
10GB - 3000GB
2048
2core 4GiB
10GB - 3000GB
2048
2core 6GiB
10GB - 3000GB
2048
4core 8GiB
10GB - 3000GB
2048
4core 16GiB
10GB - 4000GB
2048
6core 24GiB
10GB - 4000GB
2048
8core 16GiB
10GB - 4000GB
2048
8core 32GiB
10GB - 4000GB
4000
8core 48GiB
10GB - 4000GB
4500
8core 64GiB
10GB - 4500GB
5500
12core 24GiB
10GB - 8000GB
2048
12core 64GiB
10GB - 8000GB
5500
16core 32GiB
10GB - 8000GB
4000
16core 96GiB
10GB - 8000GB
8000
20core 128GiB
10GB - 8000GB
10000
24core 48GiB
10GB - 8000GB
4500
24core 192GiB
10GB - 8000GB
12000
28core 240GiB
10GB - 8000GB
13000
32core 64GiB
10GB - 8000GB
5500
48core 480GiB
10GB - 8000GB
22000
64core 256GiB
10GB - 8000GB
13000
64core 384GiB
10GB - 8000GB
20000
64core 512GiB
10GB - 8000GB
22000
90core 720GiB
10GB - 8000GB
36000
Note:
The Shanghai Zone 5, Guangzhou Zone 4, Guangzhou Zone 6 and Guangzhou Zone 7 support larger storage specifications: 48-core 480 GiB, with disk capacity up to 16000 GB.
前の記事へ: Billing Overview次の記事へ: Purchase Methods

ヘルプとサポート

この記事はお役に立ちましたか？

フィードバック