Re: Log timestamps at higher resolution

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: 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 13:58:58
Message-ID: 20181024135858.imephphm5j5z7n7z@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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).

> Baroque is OK for music if you're in the mood,

Haha!

> I suspect that as things Cloud™ (a.k.a. Renting Other People's Data
> Centers) get even more popular, we'll want to improve our logging
> game, and that will sooner rather than later have features complicated
> enough to be worth testing.

Improved logging is already a sore need we have, regardless of weather
conditions.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2018-10-24 14:06:57 Estimating number of distinct values.
Previous Message Christian Ullrich 2018-10-24 13:45:50 Problem with EDB 11.0 Windows x64 distributions