Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-14095

Message/event timestamp should zero pad the microseconds

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • WT12.0.0, 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines

      When debugging through format ops tracing output, which is often overwhelmingly large, I commonly do something similar to grep <thread1> fulltrace > trace. thread1 and grep <thread2> fulltrace > trace.thread2 and then cat trace.thread* | sort > trace.mythreads

      The problem is that the timestamps sort poorly because the microsecond portion is not zero-padded. It is a small change to add to the printf format string to print six microsecond digits and zero pad the output.

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: