Re: microsecond log timestamps

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
Cc: pggeneral <pgsql-general(at)postgresql(dot)org>
Subject: Re: microsecond log timestamps
Date: 2001-05-12 18:05:44
Message-ID: 10377.989690744@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches

Ed Loehr <eloehr(at)austin(dot)rr(dot)com> writes:
> Someone probably had a good reason for doing this, but looking at
> backend/utils/error/elog.c line 592 in 7.1, it looks like the pre-7.1
> capability for microsecond timestamp granularity (e.g.,
> 20010511.14:23:49.325) in tprintf_timestamp() was removed in favor of a
> coarser 1-second resolution using time_t in print_timestamp()? Is that
> correct? If not, what am I missing?

> If so, is anyone aware of an existing patch to give sub-second log
> timestamp capability? Microsecond granularity has been very helpful for
> query timing.

I can't see any good reason that print_timestamp() shouldn't use
gettimeofday() rather than time(); certainly there's no portability
argument for it, because we use gettimeofday in several other places.

Feel free to submit a patch...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-05-12 20:22:27 Re: COPY locking
Previous Message Tom Lane 2001-05-12 17:15:17 Re: about new join syntax performance

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2001-05-12 20:25:52 Re: Changes needed to build on NetBSD
Previous Message Ed Loehr 2001-05-11 22:19:31 Re: microsecond log timestamps