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

Jelte Fennema-Nio <postgres@jeltef.nl>

From: Jelte Fennema-Nio <postgres@jeltef.nl>

To: Peter Eisentraut <peter@eisentraut.org>

Cc: Aleksander Alekseev <aleksander@timescale.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, "Andrey M. Borodin" <x4mmm@yandex-team.ru>

Date: 2024-03-20T18:35:20Z

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

On Wed, 20 Mar 2024 at 07:35, Peter Eisentraut <peter@eisentraut.org> wrote:
> If we want to be robust without any guarantees from gettimeofday(), then
> arguably gettimeofday() is not the right underlying function to use for
> UUIDv7.

There's also clock_gettime which exposes its resolution using clock_getres