Technical Analysis: Resolving Maximum Execution Time Exceeded Error in phpMyAdmin

Problem Background and Error Analysis

When executing large-scale data queries in phpMyAdmin, users frequently encounter the "Maximum execution time of 60 seconds exceeded" error. This error typically occurs when processing large database tables containing millions of records, such as the user-mentioned table with over 9 million records.

From a technical perspective, this error involves multiple layers of execution time limitations: PHP's max_execution_time configuration, phpMyAdmin's $cfg['ExecTimeLimit'] setting, and web server timeout configurations. When query execution time exceeds the minimum value among these limitations, the system interrupts execution and throws an error.

Core Solution: Modifying ExecTimeLimit Configuration

Based on best practices and user feedback, the most effective solution is to modify phpMyAdmin's $cfg['ExecTimeLimit'] configuration parameter. This parameter specifically controls the maximum execution time for phpMyAdmin internal scripts, independent of PHP's system-level configuration.

Detailed implementation steps:

1. Locate configuration file: In XAMPP environment, find the xampp\phpMyAdmin\libraries\config.default.php file
2. Find configuration item: Search for the $cfg['ExecTimeLimit'] parameter in the file
3. Modify value: Change the default value 600 to a higher number, such as 6000 (representing 6000 seconds)
4. Save and restart: Save the modifications and restart Apache service for the configuration to take effect

Technical principle analysis: The $cfg['ExecTimeLimit'] parameter uses phpMyAdmin's internal timing mechanism to periodically check elapsed time during script execution. When detected execution time exceeds the set value, it gracefully terminates the operation rather than relying on PHP's system-level interruption.

Configuration Parameter Details and Best Practices

The $cfg['ExecTimeLimit'] parameter accepts integer values in seconds:

• Setting to 0 indicates no time limit
• Recommended value range: For large database operations, suggest setting to 3600 (1 hour) or higher
• Reasonable configuration should consider server resources and actual business requirements

Example configuration code:

// Set in config.default.php or config.inc.php
$cfg['ExecTimeLimit'] = 6000; // Set to 100 minutes

Supplementary Configuration Optimization Recommendations

While modifying $cfg['ExecTimeLimit'] is the primary solution, to ensure overall system performance, it's recommended to simultaneously optimize the following configurations:

PHP configuration optimization (php.ini file):

max_execution_time = 5000
max_input_time = 5000
memory_limit = 1000M
post_max_size = 750M
upload_max_filesize = 750M

MySQL configuration optimization (my.ini file):

max_allowed_packet = 200M

Error Troubleshooting and Verification Methods

After modifying configurations, it's recommended to verify effectiveness through the following methods:

1. Check configuration status using phpMyAdmin interface
2. Create test queries to verify execution time limits
3. Monitor server resource usage to ensure configuration modifications don't cause system overload

If the problem persists, check:

• Whether configuration files are correctly loaded
• Web server timeout settings
• Database connection and query optimization

Technical Summary

By systematically analyzing and configuring the $cfg['ExecTimeLimit'] parameter, the execution time exceeded error in phpMyAdmin can be effectively resolved. This method is specifically optimized for phpMyAdmin's unique requirements, making it more precise and effective than simply modifying PHP system configurations. It's recommended to make appropriate parameter adjustments based on specific business requirements and data scale in practical applications.