Bug #102903 | CTAS or ITAS - max_execution_time | ||
---|---|---|---|
Submitted: | 10 Mar 2021 13:50 | Modified: | 7 Aug 2021 18:12 |
Reporter: | Matias Sánchez | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S4 (Feature request) |
Version: | MySQL 8.0.22 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | max_execution_time |
[10 Mar 2021 13:50]
Matias Sánchez
[10 Mar 2021 13:57]
MySQL Verification Team
Hello Matias, Thank you for feature request. regards, Umesh
[7 Aug 2021 18:12]
Matias Sánchez
Hi guys!! :) Could you tell us if this feature request is being considered on short term dev & releases? For our platform, this "max_execution_time limit" for any kind of statement is needed, mostly on "create temporary table as select" statements because we rely on many dynamic temp table creations but we need also to have max_execution_time there. Just tested on 8.0.26 and create temporary table tmp_version (id int) as SELECT /*+ MAX_EXECUTION_TIME(1) */ VERSION from INFORMATION_SCHEMA.TABLES; is not returning "Query execution was interrupted" as it should for it's select part; when the select itself does mysql> SELECT /*+ MAX_EXECUTION_TIME(1) */ VERSION from INFORMATION_SCHEMA.TABLES;; ERROR 3024 (HY000): Query execution was interrupted, maximum statement execution time exceeded We appreciate any news :) Best regards.