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_execution_time

max_execution_time

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

Feature Description

max_execution_time is used to set the execution timeout duration for SELECT statements, in milliseconds. When the execution time of a SELECT statement exceeds the value set by max_execution_time, the query will be interrupted and an error will be returned.
Use cases of the max_execution_time parameter:
For read-only SELECT statements, the max_execution_time parameter applies to all queries unless the query contains the MAX_EXECUTION_TIME(N) optimizer hint or N is 0.
For non-read-only SELECT statements (for example, calling stored functions with side effects), the max_execution_time parameter does not apply.
For SELECT statements within stored programs, the max_execution_time parameter does not apply.
When adjusting the max_execution_time parameter, you need to consider the following factors:
Script execution time: Set appropriate values according to the actual execution time of the script. For scripts that take a long time to execute, the value of max_execution_time may need to be increased to ensure that the script can run normally. For scripts that take a short time to execute, the value of max_execution_time can be reduced to save system resources.
System resources: Set appropriate values according to the actual resource situation of the server. When resources are sufficient, the value of max_execution_time can be increased appropriately to improve script execution efficiency. In the case of resource shortage, the value of max_execution_time needs to be reduced to avoid resource exhaustion.
User experience: Set appropriate values according to the actual needs and experience of users. For applications with high requirements for user experience, the value of max_execution_time may need to be increased to ensure that script execution is completed within a reasonable time. For applications with low requirements for user experience, the value of max_execution_time can be reduced to improve system performance.

Attribute Description

Required
Description
Parameter Type
ULONG
Default Value
0
Value Range
0 ~ 18446744073709551615
Effective Scope
GLOBAL
SESSION
Restart Required
No
이전 주제: max_connections다음 주제: max_prepared_stmt_count

도움말 및 지원

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

피드백