Bug #17494 The algorithm for calculating execution times is not fully correct

Submitted:	16 Feb 2006 20:07	Modified:	8 Apr 2006 5:41
Reporter:	Andrey Hristov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S2 (Serious)
Version:	5.1.7	OS:
Assigned to:	Andrey Hristov	CPU Architecture:	Any

Description:
The calculation should be corrected so it should count from STARTS instead of LAST_EXECUTED_AT

How to repeat:
..

When this is fixed close bug #17493

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3636

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/4089

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/4592

Fixed in 5.1.7, now the calculation is fixed. Intermediate server(scheduler) stops and starts does not affect the activation times.

Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Additional info:

Documented bugfix in 5.1.7 changelog. Closed.

Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.