| From: | Hannu Krosing <hannuk(at)google(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: What is a typical precision of gettimeofday()? |
| Date: | 2024-07-03 10:31:27 |
| Message-ID: | CAMT0RQT_kaQK=xVtxPihSjPEsEq2TiPrpoLAu_5HpLp68VwWxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 3, 2024 at 10:03 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
Keep in mind also that instr_time.h does not pretend to provide
> real time --- the clock origin is arbitrary. But these results
> do give me additional confidence that gettimeofday() should be
> good to the microsecond on any remotely-modern platform.
The only platform I have found where the resolution is only a
microsecond is RISC-V ( https://www.sifive.com/boards/hifive-unmatched
)
Everywhere else it seems to be much more precise.
--
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2024-07-03 10:32:05 | Re: Conflict Detection and Resolution |
| Previous Message | Amit Kapila | 2024-07-03 10:05:28 | Re: Conflict Detection and Resolution |