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 Replica 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 GuideNetwork ManagementEnabling Public Network Services Through CLB

Enabling Public Network Services Through CLB

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-11 15:07:27
TencentDB for PostgreSQL supports two address types: private network address and public network address. The private network address is provided by default for internal access to the instance. If public network access is required, you can enable the public network address via the Console or enable public network services through Cloud Load Balancer (CLB).
This introduces the method to enable public network services through CLB and connect to the instance via the pgAdmin client.
Note:
Currently, public network addresses can be enabled through the console in the following regions: Beijing, Chengdu, Guangzhou, Hong Kong (China), Nanjing, Shanghai, Tokyo, and Silicon Valley.
- After enabling the public network address, you must configure security group rules to access.

Prerequisites

Applied for backend service feature usage. Please submit a ticket to CLB to apply for backend service feature usage.
The CLB service has been purchased. For specific steps, please see CLB purchase method.
Note:
When purchasing the CLB service, select the service region where TencentDB for PostgreSQL is located.
Only public network CLB instances support backend service functionality. The network type must be set to public network.
Note: When creating a CLB instance, please ensure it belongs to the same VPC as the TencentDB for PostgreSQL instance. If they are in different VPCs, configure CCN to connect the private networks after creating the CLB instance. For details, please refer to Configure CCN.

Step 1: Enable CLB Backend Service

Enable cross-VPC access so that the CLB instance can be bound to another private IP.
Log in to the CLB console, select the region, and click the target instance ID in the instance list to enter the instance management page.
On the Basic Info page, click Configure in the Real Server section.
In the pop-up window, click Submit.

Step 2: Configure CLB Service

On the instance management page, select Listener Management, and click Create under TCP/UDP/TCP SSL/QUIC listener.

In the pop-up dialog box, complete the settings step by step, and finally click Submit to complete the creation.

After creation, click the just created listener, then click Bind.
In the pop-up dialog box, select the target type as IP Type, click Add Private IP, input the private IP address and port of the PostgreSQL instance to be connected, then click OK to complete the binding.
Note:
If unable to bind, Submit a Ticket for assistance.

Step 3: Configure TencentDB for PostgreSQL Security Group

Log in to the TencentDB for PostgreSQL console, select a region, and click Instance ID or Operation > Manage in the instance list to enter the instance management page.
On the instance management page, select the Security Group tab, click Configure Security Group, add a new security group, set the security group rules to allow all ports, and confirm the security group permits public IP access. For detailed configuration methods, please refer to Manage Security Group.



Step 4: Connecting to an Instance Via pgAdmin Client

Enter the pgAdmin client official download page, choose to download based on your OS type, and complete installation.

After installation, open pgAdmin4, click Add New Server on the homepage, and fill in the instance information to be connected.

The information description is as follows:
Parameter
Description
Host name/address
Enter the address of the CLB instance. You can view the VIP information in the basic info on the CLB instance details page.
Port
Enter the port of the CLB instance. You can view the TCP port number under Monitor Management on the CLB instance details page.
Username
Enter the account name of the PostgreSQL instance to be connected. The account is created under Instance Management > Database Management > Account Management.
Password
Enter the password corresponding to the filled-in Username, then click Save.

Connection successful. The interface is shown in the figure below.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan