From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
---|---|
To: | pggeneral <pgsql-general(at)postgreSQL(dot)org> |
Subject: | microsecond log timestamps |
Date: | 2001-05-11 22:10:25 |
Message-ID: | 3AFC6351.4ECDD31B@austin.rr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
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.
Regards,
Ed Loehr
From | Date | Subject | |
---|---|---|---|
Next Message | Ed Loehr | 2001-05-11 22:19:31 | Re: microsecond log timestamps |
Previous Message | Peter Eisentraut | 2001-05-11 21:55:43 | Re: PL/Perl without shared libperl.a |
From | Date | Subject | |
---|---|---|---|
Next Message | Ed Loehr | 2001-05-11 22:19:31 | Re: microsecond log timestamps |
Previous Message | Jason Tishler | 2001-05-11 15:30:30 | Cygwin PostgreSQL Python Module Patch |