TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
DocumentationTencentDB for MySQLOperation GuideParameter ConfigurationModification Records of System Parameter Templates
Modification Records of System Parameter Templates
Last updated: 2024-12-30 17:48:56
TencentDB for MySQL provides system parameter templates for batch parameter settings. The parameters in system parameter templates may be optimized and updated with MySQL iteration. This document describes the update history of the parameters in system parameter templates.
Note:
If the parameters in the template are updated, the instance parameters are not updated unless they are manually re-applied to the instances. You can apply the parameter changes to single or multiple instances by importing a template.
For directions on how to use system parameter templates, see Managing Parameter Template.
December 2024
Parameter name | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_stats_persistent_sample_pages | ✓ | ✓ | ✓ | Involved template: high-stability/high-performance Involved engine: InnoDB Before change Default Value: 20 After change Default Value: 200 |
November 2024
Parameter name | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
explicit_defaults_for_timestamp | ✓ | ✓ | ✓ | Involved template: high-stability/high-performance Involved engine: InnoDB and RocksDB Before change Whether to restart to take effect: Yes After change Whether to restart to take effect: No |
innodb_page_cleaners | - | ✓ | ✓ | Involved template: high-stability/high-performance Involved engine: InnoDB Before change Default value: 4 After change Default value: 8 |
September 2024
Parameter Name | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_table_drop_mode | ✓ | ✓ | Involved template: high-stability Involved engine: InnoDB Before change Default value: SYNC_DROP After change Default value: ASYNC_DROP |
March 2024
Parameter Name | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
slave_parallel_workers | ✓ | ✓ | ✓ | Involved template: High-performance/high-stability Involved engines: InnoDB/RocksDB Before change Parameter range: [0 | 1 | 2 | 4 | 8 | 16 | 32 | 64] Default value: 0 After change Parameter range: [0-64] Default value: {MIN(DBInitCpu*2,64)} |
January 2024
Parameter | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
thread_pool_oversubscribe | ✓ | ✓ | ✓ | Changes in default value of thread_pool_oversubscribe parameter in high-performance parameter templates for MySQL 5.6, 5.7, 8.0. Previous default value: 10 Updated default value: 16 |
December 2023
Parameter | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
thread_pool_oversubscribe | ✓ | ✓ | ✓ | The default value for the parameter 'thread_pool_oversubscribe' has been modified. Previous default value: 3 Updated default value: 10 |
August 2023
Parameter | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_fast_ahi_cleanup_for_drop_table | ✓ | ✓ | The default value for the parameter 'innodb_fast_ahi_cleanup_for_drop_table' has been altered. Previous default value: OFF Updated default value: ON |
June 2023
Parameter | MySQL 5.5 | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
time_zone | ✓ | ✓ | ✓ | ✓ | Modification of default value for the 'time_zone' parameter Previous default value: SYSTEM Updated default value: +8:00 |
May 2023
Parameter | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_async_truncate_work_enabled | ✓ | - | Asynchronous table deletion function switch parameter modification for version 5.7 The parameter has been changed from innodb_async_truncate_work_enabled to innodb_table_drop_mode. (May 15, 2023) |
innodb_parallel_ddl | - | ✓ | Parameter deprecation (May 5, 2023) |
March 2023
Parameter | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_temp_data_file_path | ✓ | ✓ | Modification of default value for innodb_temp_data_file_path Parameter Prior default value：ibtmp1:12M:autoextend Altered default value：ibtmp1:12M:autoextend:max:1048576M |
January 2023
Parameter | MySQL 5.7 | MySQL 8.0 | Change Description |
max_execution_time | ✓ | ✓ | Dynamic setting is supported for max_execution_timeRestart required: No Default value: 0Value range: 0–4294967295 Unit: ms |
August 2022
Parameter | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_buffer_pool_size | ✓ | ✓ | Dynamic setting is supported for innodb_buffer_pool_sizeRestart required: No Default value: {DBInitMemory * 786432} Value range: {DBInitMemory * 524288} - {DBInitMemory * 943718} DBinitMemory: An integer of instance memory size |
July 2022
Parameter | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_temp_data_file_path | ✓ | ✓ | Parameter modification is supported for innodb_temp_data_file_path (temp tablespace size) and the parameter properties are as follows: Restart required: Yes Default value: ibtmp1:12M:autoextendValue range of ibtmp: 12 MB - 1024 MB. After you select autoextend, the maximum value can be set to 2097152 MB |
March 2022
Parameter | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
innodb_open_files | ✓ | ✓ | ✓ | Removed |
innodb_stats_sample_pages | - | ✓ | ✓ | Removed |
wait_timeout | ✓ | ✓ | ✓ | New value range: 1–31536000 |
thread_cache_size | ✓ | ✓ | ✓ | New value range: 1–16384 |
December 2021
Parameter | MySQL 5.6 | MySQL 5.7 | MySQL 8.0 | Change Description |
binlog_row_image | ✓ | ✓ | ✓ | Default value: FULL. For the early created instances, the default value is MINIMAL. Manual modification is supported. |
November 2020
Parameter | MySQL 8.0 | Change Description |
iinnodb_flush_log_at_trx_commit | ✓ | Parameter added |
sync_binlog | ✓ | Parameter added |
local_infile | ✓ | Parameter added |
innodb_log_file_size | ✓ | Parameter added |
cdb_recycle_bin_enabled | ✓ | Parameter added |
binlog_format | ✓ | New value range: row |
innodb_autoinc_lock_mode | ✓ | New default value: 2 |
table_open_cache | ✓ | New default value: 2000 |
slave_pending_jobs_size_max | ✓ | New default value: 1073741824 |
time_zone | ✓ | New value range: [SYSTEM|-12:00|-11:00|-10:00|-09:00|-08:00|-07:00|-06:00| -05:00|-04:00|-03:00|-02:00|-01:00|+00:00|+01:00|+02:00|+03:00|+04:00|+05:00| +05:30|+06:00|+06:30|+07:00|+08:00|+09:00|+10:00|+11:00|+12:00|+13:00] |
max_connections | ✓ | New value range: 1–100000 |
slave_rows_search_algorithms | ✓ | New default value: TABLE_SCAN,INDEX_SCAN,HASH_SCAN |
innodb_open_files | ✓ | New default value: 10240 |
slave_parallel_type | ✓ | New value range: LOGICAL_CLOCK|TABLE|DATABASE |
August 2020
Parameter | MySQL 5.6 | MySQL 5.7 | Change Description |
log_warnings | ✓ | ✓ | Parameter added |
innodb_flush_log_at_trx_commit | ✓ | ✓ | Parameter added |
sync_binlog | ✓ | ✓ | Parameter added |
local_infile | ✓ | ✓ | Parameter added |
innodb_log_file_size | ✓ | ✓ | Parameter added |
binlog_format | ✓ | ✓ | New range value: row |
innodb_autoinc_lock_mode | ✓ | ✓ | New default value: 2 |
innodb_open_files | ✓ | ✓ | New value range: 1–102400 |
table_open_cache | ✓ | ✓ | New default value: 2000 |
slave_pending_jobs_size_max | ✓ | ✓ | New default value: 1 GB |
time_zone | ✓ | ✓ | New value range: [SYSTEM|-12:00|-11:00|-10:00|-09:00|-08:00|-07:00|-06:00| -05:00|-04:00|-03:00|-02:00|-01:00|+00:00|+01:00|+02:00|+03:00|+04:00|+05:00| +05:30|+06:00|+06:30|+07:00|+08:00|+09:00|+10:00|+11:00|+12:00|+13:00] |
max_connections | ✓ | ✓ | New value range: 1–100000 |
cdb_more_gtid_feature_supported | - | ✓ | All kernel features supported |
cdb_more_gtid_feature_supported | ✓ | - | New default value: off |
slave_parallel_workers | - | ✓ | All kernel features supported |
tls_version | - | ✓ | Removed |
slave_rows_search_algorithms | ✓ | ✓ | New default value: TABLE_SCAN,INDEX_SCAN,HASH_SCAN |
innodb_open_files | ✓ | ✓ | New default value: 10240 |
August 2020
Parameter | MySQL 5.5 | Change Description |
innodb_autoinc_lock_mode | ✓ | New default value: TABLE_SCAN,INDEX_SCAN,HASH_SCAN |
innodb_open_files | ✓ | New default value: 10240 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No