tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Kernel Overview

PDF
Focus Mode
Font Size
Last updated: 2026-03-17 11:16:56
TDSQL-C for MySQL supports the multi-engine feature. The TXSQL engine is 100% compatible with native MySQL, allowing you to migrate MySQL databases to TDSQL-C for MySQL without modifying any application code or configuration. The TXSQL engine is the default engine and can be used for both read-write and read-only instances. The LibraDB engine also supports most MySQL syntax and serves users through read-only instances.
The TXSQL engine kernel also provides various MySQL Enterprise features, such as database audit, thread pool, encryption function, backup, and recovery. The TXSQL engine deeply optimizes the InnoDB storage engine and query optimization, enhancing the database's usability and maintainability. While providing all MySQL features, it also offers enterprise-grade features like disaster recovery, restoration, monitoring, performance optimization, read-write separation, and database audit.
The other engine, LibraDB, is a proprietary engine designed for real-time analysis scenarios. The LibraDB engine supports massive parallelism, vectorized execution engine, and columnar storage, providing high-performance complex data analysis and queries. It supports real-time data queries through read-only instances, avoiding the complexity of ETL components and long data latency. As a pluggable engine, LibraDB can be created within TDSQL-C for MySQL 5.7 and 8.0 clusters (clusters with pre-configured resources).

More information of the TXSQL engine kernel version

For updates of the TXSQL engine kernel version, refer to TXSQL Engine Kernel Version Release Notes.
Automatic and manual upgrade of the kernel version are supported. For instructions and details, refer to Upgrading Kernel Minor Versions.

More information of the LibraDB engine kernel version

For updates of the LibraDB engine kernel version, refer to LibraDB Engine Kernel Version Release Notes.

More information of the database proxy version

For updates of the database proxy version, refer to Database Proxy Version Release Notes.
The database proxy version can be upgraded. For details, refer to Upgrading Database Proxy Minor Versions.

TXSQL engine kernel version release notes

TXSQL Engine Version 8.0
TXSQL Engine Version 5.7
Database Kernel Version
Release Date
3.1.17.002
2025-12
3.1.17.001
2025-10
3.1.16.006
2026-03
3.1.16.003
2025-09
3.1.16.002
2025-07
3.1.16.001
2025-05
3.1.15.006
2025-03
3.1.15.005
2025-02
3.1.15.004
2024-11
3.1.15.003
2024-10
3.1.15.002
2024-10
3.1.15.001
2024-10
3.1.15
2024-08
3.1.14
2024-05
3.1.13
2024-04
3.1.12
2024-01
3.1.10
2023-06
3.1.9
2022-11
3.1.8
2022-10
3.1.7
2022-09
3.1.6
2022-08
3.1.5
2022-07
3.1.3
2022-06
3.1.2
2022-02
3.1.1
2021-11
3.0.1
2021-08
Database Kernel Version
Release Date
2.1.14.001
2025-12
2.1.13.002
2025-02
2.1.13.001
2024-10
2.1.12
2024-01
2.1.11
2024-01
2.1.10
2023-07
2.0.23/2.1.9
2023-05
2.0.22/2.1.8
2022-11
2.0.21/2.1.7
2022-09
2.0.20/2.1.6
2022-08
2.0.19
2022-07
2.0.17
2022-06
2.0.16
2022-01
2.0.15
2021-10
2.0.14
2021-07
2.0.13
2021-03
2.0.12
2020-11
2.0.11
2020-06

LibraDB engine kernel version release notes

Read-only Analysis Engine - LibraDB Engine Version
Release Date
4.2509.1.0
2025-12
4.2506.2.0
2025-11
4.2506.1.0
2025-10
3.2503.7.0
2025-10
3.2503.6.0
2025-10
3.2503.5.0
2025-09
3.2503.4.0
2025-08
3.2503.1.0
2025-07
2.2410.14.0
2025-11
2.2410.13.0
2025-10
2.2410.12.0
2025-09
2.2410.11.1
2025-08
2.2410.10.1
2025-08
2.2410.8.0
2025-06
2.2410.7.0
2025-06
2.2410.6.0
2025-05
2.2410.5.0
2025-04
2.2410.4.1
2025-03
2.2410.4.0
2025-03
2.2410.3.0
2025-03
2.2410.2.0
2025-03
2.2410.1.0
2025-02
1.2404.24.0
2025-05
1.2404.23.0
2025-04
1.2404.22.1
2025-03
1.2404.22.0
2025-03
1.2404.21.0
2025-02
1.2404.20.0
2025-01
1.2404.19.1
2024-12
1.2404.19.0
2024-12
1.2404.17.0
2024-12
1.2404.16.0
2024-11
1.2404.15.2
2024-11
1.2404.15.1
2024-10
1.2404.10.0
2024-09
1.2404.7
2024-08

Database proxy version release notes

Database Proxy Version
Release Date
1.4.5
2025-09
1.4.4
2025-03
1.3.20
2025-12
1.3.19
2025-07
1.3.17
2025-05
1.3.16
2025-03
1.3.15
2024-12
1.3.14
2024-11
1.3.13
2024-08
1.3.12
2024-06
1.3.10
2024-03
1.3.8
2023-10
1.3.7
2023-05
1.3.5
2022-11
1.3.4
2022-09
1.3.3
2022-08
1.2.1
2022-07

Help and Support

Was this page helpful?

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

Feedback