Horton

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

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

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vik Fearing <vik@postgresfriends.org>
Cc: Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>, hannuk@google.com, x4mmm@yandex-team.ru
Date: 2025-07-08T00:37:15Z
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 →

  1. Force LC_NUMERIC to C while running TAP tests.

  2. Minor tweaks for pg_test_timing.

  3. Change pg_test_timing to measure in nanoseconds not microseconds.

Vik Fearing <vik@postgresfriends.org> writes:
> Having read through this thread, is there any chance at all that we 
> might be able to implement feature F555, “Enhanced seconds precision”?

Don't see how we could do that without an on-disk compatibility break
for timestamps.  Also, AFAICS there's no way to stuff nanosecond
precision and a reasonable timestamp range (at least a few thousand
years IMO) into 64 bits, so the compatibility break would include
expending more disk space.  Hard to believe that it's worth it.

(If we did decide to break compatibility, my own first priority
would be to make timestamptz actually include a timezone ...)

			regards, tom lane