TencentDB for PostgreSQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Kernel Version Introduction
- Operation Guide
- Instance Management
- Upgrading Instance
- Read-Only Instance
- Account Management
- Database Management
- Database Optimization
- Parameter Management
- Log Management and Analysis
- Backup and Restoration
- Data Migration
- DTS-Based Logical Migration
- Verification Failure Handling
- Physical migration based on DTS
- Database Audit
- Extension Management
- Supported Extensions
- Network Management
- Data Security
- Tenant and Resource Isolation
- Monitoring and Alarms
- MSSQL Compatible Version
- Practical Tutorial
- Performance White Paper
- API Documentation
- Making API Requests
- Instance APIs
- Read-only Replica APIs
- Backup and Recovery APIs
- Parameter Management APIs
- Security Group APIs
- Performance Optimization APIs
- Specification APIs
- PostgreSQL for Serverless APIs
- Network APIs
- Service Agreement
Instance Type and Specification
Last updated: 2024-12-09 11:33:52
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), read-only instance | 10,11,12,13,14,15,16 | 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 |
Note:
The Shanghai Zone 5, Guangzhou Zone 4, and Guangzhou Zone 6 support larger storage specifications:
20-core 128 GiB, with disk capacity up to 7000 GB.
28-core 240 GiB, with disk capacity up to 8000 GB.
48-core 480 GiB, with disk capacity up to 16000 GB.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No