From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Log timestamps at higher resolution |
Date: | 2018-10-24 14:17:09 |
Message-ID: | 19848.1540390629@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2018-Oct-24, David Fetter wrote:
>> For another, having separate letter rather than number modifiers as
>> printf("%03d") does, is just lousy API design.
> I don't think the API is lousy as all that, but a further improvement to
> allow a precision specifier might be a worthy feature addition -- say
> %.6t or such (where %m would have the same meaning as %.3t).
+1. I think the patch as it stands is way too influenced by the purely
chance factor that "milli" and "micro" have the same initial letter in
English. David would never have submitted it in this form if that weren't
true; but that doesn't make either resolution the right answer for
everyone. And I do not want to have this discussion again in ten years
when somebody starts moaning that microsecond resolution is so last
century. Let's put in a number so that the format-string API can stay the
same as the required resolution moves.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2018-10-24 14:21:56 | Re: Log timestamps at higher resolution |
Previous Message | Konstantin Knizhnik | 2018-10-24 14:06:57 | Estimating number of distinct values. |