Re: What is a typical precision of gettimeofday()?

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Hannu Krosing <hannuk@google.com>

Cc: "Andrey M. Borodin" <x4mmm@yandex-team.ru>, Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-07-08T15:25:01Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Force LC_NUMERIC to C while running TAP tests.
- f25792c541e5 19 (unreleased) landed
Minor tweaks for pg_test_timing.
- 9dcc7641444f 19 (unreleased) landed
Change pg_test_timing to measure in nanoseconds not microseconds.
- 0b096e379e6f 19 (unreleased) landed

Hannu Krosing <hannuk@google.com> writes:
> On Mon, Jul 7, 2025 at 11:38 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What do you think of instead specifying the limit as the maximum
>> running-percentage to print, with a default of say 99.99%?  That
>> gives me results like

> I agree that percentage covered is a much better metric indeed.
> And I am equally ok with a default of either 99.9% or 99.99%.

OK, pushed after a bit more fooling with the documentation.

			regards, tom lane