log_checkpoints, microseconds - Mailing list pgsql-bugs

From Peter Geoghegan
Subject log_checkpoints, microseconds
Date
Msg-id CAM3SWZSeqmy7YP71uZuYHiiRWXz_UTNF3GxSPAzE9mUH3c5d0w@mail.gmail.com
Whole thread Raw
Responses Re: log_checkpoints, microseconds  (John R Pierce <pierce@hogranch.com>)
List pgsql-bugs
The following code appears within md.c:

if (seg != NULL &&
    FileSync(seg->mdfd_vfd) >= 0)
{
    /* Success; update statistics about sync timing */
    INSTR_TIME_SET_CURRENT(sync_end);
    sync_diff = sync_end;
    INSTR_TIME_SUBTRACT(sync_diff, sync_start);
    elapsed = INSTR_TIME_GET_MICROSEC(sync_diff);
    if (elapsed > longest)
        longest = elapsed;
    total_elapsed += elapsed;
    processed++;
    if (log_checkpoints)
        elog(DEBUG1, "checkpoint sync: number=%d file=%s time=%.3f msec",
             processed,
             FilePathName(seg->mdfd_vfd),
             (double) elapsed / 1000);

    break;    /* out of retry loop */
}

Did the author of this code really intend that "elapsed" microseconds
be divided by 1000 like this?
--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #8695: Reloading dump fails at COMMENT ON EXTENSION plpgsql
Next
From: John R Pierce
Date:
Subject: Re: log_checkpoints, microseconds