tencent cloud

TDSQL Boundless

Release Notes
Product Introduction
Overview
Scenarios
Product Architecture
Instance Types
Compatibility Notes
Usage specification recommendations
Kernel Features
Kernel Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Billing
Billing Overview
Purchase Method
Pricing Details
Renewal
Overdue Payments
Refund
Getting Started
Creating an Instance
Connect to Instances
User Guide
Data Migration
Data Subscription
Instance Management
Parameter Configuration
Account Management
Security Group
Backup and Restoration
Database Auditing
Tag Management
Use Cases
Technical Evolution and Usage Practices of Online DDL
Lock Mechanism Analysis and Troubleshooting Practices
Data Intelligent Scheduling and Related Practices for Performance Optimization
TDSQL Boundless Selection Guide and Practical Tutorial
Developer Guide
Developer Guide (MySQL Compatibility Mode)
Developer Guide (HBase Compatibility Mode)
Performance Tuning
Performance Tuning Overview
SQL Tuning
DDL Tuning
Performance White Paper
Performance Overview
TPC-C Test
Sysbench Test
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Security Group APIs
Task APIs
Backup APIs
Rollback APIs
Parameter APIs
Database APIs
Data Types
Error Codes
General Reference
System Architecture
SQL Reference
Database Parameter Description
TPC-H benchmark data model reference
Error Code Information
Security and Compliance
FAQs
Agreements
Service Level Agreement
Terms of Service
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
문서TDSQL BoundlessGeneral ReferenceDatabase Parameter Descriptionmax_allowed_packet

max_allowed_packet

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-27 15:01:19

Feature Description

max_allowed_packet sets the maximum packet size allowed during data transmission between the SQLEngine and clients, measured in bytes. When a client sends a packet exceeding the value of max_allowed_packet, the SQLEngine will reject the packet.
When adjusting the max_allowed_packet parameter, you need to consider the following factors:
System resources: Set appropriate values according to the actual resource situation of the server. When resources are sufficient, the value of max_allowed_packet can be appropriately increased to improve the system's concurrent processing capacity. In the case of resource shortage, the value of max_allowed_packet needs to be reduced to avoid resource exhaustion.
Application requirements: Set appropriate values based on the actual needs of the application. For applications with high requirements for packet size, the value of max_allowed_packet may need to be increased to meet concurrency requirements. For applications with low requirements for data packet size, the value of max_allowed_packet can be reduced to save system resources.
Database performance: Set appropriate values based on the actual performance of the database. For databases with good performance, the value of max_allowed_packet may need to be increased to improve their concurrency processing capability. For databases with poor performance, the value of max_allowed_packet needs to be reduced to avoid database overload.

Attribute Description

Required
Description
Parameter Type
ULONG
Default Value
67108864
Value Range
1024 ~ 1073741824
Note:
The value of this variable should be an integer multiple of 1024. If the value is not divisible by 1024, a warning will be issued and the value will be rounded down. For example, if set to 1025, the actual value used in TDSQL Boundless will be 1024.
Effective Scope
GLOBAL
SESSION
Restart Required
No
이전 주제: long_query_time다음 주제: max_connect_errors

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백