|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||David Fetter <david(at)fetter(dot)org>|
|Cc:||Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Log timestamps at higher resolution|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
David Fetter <david(at)fetter(dot)org> writes:
> On Wed, Oct 24, 2018 at 08:00:24AM +1300, Thomas Munro wrote:
>> On Wed, Oct 24, 2018 at 7:51 AM David Fetter <david(at)fetter(dot)org> wrote:
>>> Per gripes I've been hearing with increasing frequency, please find
>>> attached a patch that implements $Subject. It's microsecond resolution
>>> because at least at the moment, nanosecond resolution doesn't appear
>>> to be helpful in this context.
>> Wouldn't you want to choose a new letter or some other way to make
>> existing format control strings do what they always did?
> I hadn't because I'd looked at the existing format as merely buggy in
> lacking precision, although I guess with really fussy log processors,
> this change could break things.
Aside from breaking things, this would increase log volume, which is
already a pain point for many people. So I think your odds of getting
it committed as-is are nil. It might be OK as a different letter, or
with some other way of controlling the precision.
regards, tom lane
|Next Message||AYahorau||2018-10-24 11:34:07||Re: Timeout parameters|
|Previous Message||Matsumura, Ryo||2018-10-24 09:43:31||RE: [PROPOSAL]a new data type 'bytea' for ECPG|