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

Kernel Version Overview

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-03-11 14:23:36
This document describes the background and strengths of TencentDB for PostgreSQL kernel versions.

Overview

PostgreSQL (PG) is a globally popular enterprise-grade open-source database. It won the DB-Engines DBMS of the Year awards for two consecutive years in 2017–2018 and again in 2020. It also won the O'Reilly Open Source Convention (OSCON) Lifetime Achievement Award in 2019.
Built on top of the community version of PostgreSQL, TencentDB for PostgreSQL offers specific features and optimized kernels based on its many years of business expertise. It not only optimizes the PostgreSQL database engine, permission management, and replication performance, but also improves the database usability and maintainability in the cloud.

Kernel Version Number

The kernel version number consists of two parts: community version number and internal version number.
v{community major version number.community minor version number}_r{incompatible version number.compatible version number}
Example: v12.7_r1.1
v stands for version, and r stands for release; for example, v12.7_r1.1 corresponds to the community version 12.7, where r1.1 indicates Tencent Cloud's iteration version composed of r{incompatible version number}.{compatible version number}.
Note:
Version: It is the PostgreSQL community version number composed of two numbers: major version and minor version. The former starts from 10 (9.3, 9.4, 9.5, 9.6, and so on), and the latter starts from 1. When a community minor version is released, Tencent Cloud will regularly follow the community to update the version.
Release: It is the version number used for TencentDB for PostgreSQL iteration and represents the modifications made by TencentDB for PostgreSQL. It consists of two numbers: incompatible version (starting from 1) and compatible version (starting from 0).
Incompatible version number
Definition of "incompatible": When a new database kernel program is used to start a database instance, if the start fails or some features cannot be used normally, the modification is incompatible. When the kernel contains incompatible features, the incompatible version number needs to be increased by 1. It will be used to determine whether the minor version upgrade can be performed directly.
Compatible version number
When a compatible modification is added, the compatible version number needs to be increased by 1.

Supported Versions

For information on the versions supported by TencentDB for PostgreSQL, refer to the Kernel Version Release Notes. You can view the database version of TencentDB for PostgreSQL via Instance List in the PostgreSQL console. For details on the version lifecycle, refer to the Large Version Lifecycle Description.

Version Rules

Version and release together form a complete version called database kernel version.
A major version corresponds to a community evolution branch iterated separately, such as 10, 11, and 12, who have their own respective version number sequence.
When the community announces that a major version will no longer be maintained, the version will become unavailable for purchase. However, Tencent Cloud will continue to support database instances running on this version until they are actively terminated or migrated.
The minor version follows the changes in the community, while the release changes according to the feature changes made by the kernel of TencentDB.

Advantages

Compared with open-source PostgreSQL, TencentDB for PostgreSQL has the following strengths:
Greater stability On the basis of open-source PostgreSQL, TencentDB for PostgreSQL further optimizes some underlying implementations of the database service, substantially reducing the problem of database crashes due to external factors and improving the database stability.
Enhanced primary-standby sync performance The primary-standby sync performance of open-source PostgreSQL is severely compromised when a high number of DDL statements are processed. TencentDB for PostgreSQL is greatly optimized in this regard, with an overall improvement of up to 30,000 times.
Shorter access latency TencentDB for PostgreSQL features special optimization for connection establishment in scenarios with a large number of non-persistent connections. This reduces the database connection performance loss by 80% and greatly improves the non-persistent connection performance.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan