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
ドキュメントTencentDB for PostgreSQLUser GuideUpgrading InstanceKernel Minor Version Upgrade

Kernel Minor Version Upgrade

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-05-21 15:53:27
TencentDB for PostgreSQL allows you to upgrade kernel minor version, so you can use new features, improve performance, or fix issues.
For detailed information on the supported kernel versions of TencentDB for PostgreSQL, please refer to Kernel Version Update History.

Overview

You can manually upgrade kernel minor version in the console.

Upgrade Rules

If an instance to be upgraded is associated with other instances (e.g., read-only instances), these instances will be upgraded together to ensure data consistency.
Version upgrade of TencentDB for PostgreSQL may involve data migration. Usually, the migration speed is related to the amount of data. Please wait patiently. During the upgrade period, your business will not be affected and can be accessed normally.

Note

Upon completion of the minor version upgrade, an active/standby switch will be involved, and the database will experience a momentary disconnection lasting a few seconds. It is recommended to perform the switch during the instance maintenance time, and the application has the automatic reconnection feature.
The kernel minor version cannot be downgraded once upgraded.

Directions

1. Log in to the TencentDB for PostgreSQL console. In the instance list, click an Instance ID or Manage in the Operation column to enter the instance details page.
2. In the Configuration Info section, click Upgrade Kernel Minor Version.

3. In the pop-up window, set the target version to upgrade and click OK.

Note:
As database kernel minor version upgrade may involve data migration, a momentary disconnection from the database may occur after the upgrade is completed. We recommend that you set the switch time to During maintenance time, so that the switch will be initiated within the next maintenance time after the upgrade is completed.
When upgrading the minor kernel version of an instance, the backend checks the Instance Parameter List. If there are data discrepancies between the parameter ranges of the target kernel version and the original kernel version, and the parameter value exceeds the range specified by the target kernel version, a notification will be provided as shown below:

前の記事へ: Kernel Minor Version Upgrade Principle Explanation次の記事へ: Upgrade the Major Version of the Database

ヘルプとサポート

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

フィードバック