• unknown's avatar
    Bug #27638: slow logging to CSV table inserts bad query_time and lock_time values · 821355da
    unknown authored
    When MySQL logged slow query information to a CSV table, it stored the
    query_time and lock_time values with an incorrect formula.
    
    If the time was over 59 seconds, this caused incorrect statistics (either the
    slow query was not logged, or the time was far from correct).  This change
    fixes the method used to store those TIME values in the slow_log table.
    
    
    mysql-test/r/log_tables-big.result:
      BitKeeper file /benchmarks/ext3/TOSAVE/tsmith/bk/maint/51/mysql-test/r/log_tables-big.result
    mysql-test/t/log_tables-big-master.opt:
      BitKeeper file /benchmarks/ext3/TOSAVE/tsmith/bk/maint/51/mysql-test/t/log_tables-big-master.opt
    mysql-test/t/log_tables-big.test:
      BitKeeper file /benchmarks/ext3/TOSAVE/tsmith/bk/maint/51/mysql-test/t/log_tables-big.test
    sql/time.cc:
      initialize all TIME fields (except neg, which may store a
      needed value) in calc_time_from_sec()
    sql/log.cc:
      Log_to_csv_event_handler::log_slow(): call store_time() instead of store() for query_time and lock_time
    include/my_time.h:
      Add TIME_MAX_VALUE_SECONDS definition
    821355da
time.cc 27.2 KB