[MDEV-7011] MAX_STATEMENT_TIME has no effect in a procedure after a previous successful statement Created: 2014-11-02 Updated: 2015-06-01 Resolved: 2015-05-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Admin statements, Data Definition - Procedure |
| Affects Version/s: | 10.1.1 |
| Fix Version/s: | 10.1.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
In the procedure below, SELECT COUNT takes clearly longer that 1 millisecond, however it is not interrupted.
Compare with this:
I saw a comment in KB which says
I'm not sure what it means, i.e. whether the whole procedure can't be measured and compared to MAX_STATEMENT_TIME, or any individual statement in the procedure cannot; in any case, the above examples show that the behavior is inconsistent. |
| Comments |
| Comment by Oleksandr Byelkin [ 2015-05-21 ] |
|
revision-id: 6efaf349adec30115bdb94b9a9927f7c5103ed99
Do not reset timer inside stored procedures and functions. — |