- THD::update_server_status uses utime_after_query too
do you know whether updating the field might cause the change of behavior somewhere else?
-
64 - query_response_time_collect(thd->utime_after_query - thd->utime_after_lock);
65 + query_response_time_collect(query_type, thd->utime_after_query - thd->start_utime);
before: utime after lock
after: start utime
why?
As discussed yesterday on IRC:
- THD::update_ server_ status uses utime_after_query too time_collect( thd->utime_ after_query - thd->utime_ after_lock) ; time_collect( query_type, thd->utime_ after_query - thd->start_utime);
do you know whether updating the field might cause the change of behavior somewhere else?
-
64 - query_response_
65 + query_response_
before: utime after lock
after: start utime
why?