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
DocumentationTencentDB for PostgreSQLUser GuideUpgrading InstanceInstructions for Upgrading Kernel Minor Version

Instructions for Upgrading Kernel Minor Version

PDF
Focus Mode
Font Size
Last updated: 2024-11-04 09:36:12

Overview

In most scenarios, kernel minor version upgrade is not mandatory. The system will provide you with the latest minor version for upgrade. For an introduction to the minor version, refer to Kernel Version Updates. You can complete the Upgrade Minor Kernel Version by yourself in the console based on your business needs.

Extreme Conditions

In extreme conditions such as major defects, security issues, or known potential risks, the system will notify you in advance via SMS, email, and the Message Center (the actual notification method is based on your Message Center subscription configuration). During the maintenance time of TencentDB for PostgreSQL instances, the system will automatically initiate and complete the mandatory upgrade of the database kernel minor version.

Impact of Kernel Minor Version Upgrades

If the instances of the kernel version to be upgraded are associated with other instances (read-only instances), the upgrade will be performed for these instances together to ensure data replication consistency.
TencentDB for PostgreSQL version upgrade may involve data migration. The migration speed typically depends on data volume. Your business will not be affected during upgrade and will be accessible as usual.
Upon completion of minor version upgrades, instance switching will occur, which may cause momentary disconnection. You are recommended to enable the automatic reconnection feature of applications.
You are recommended to Set Instance Maintenance Time via the console or API to avoid mandatory upgrades during business peak periods.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback