Re: [HACKERS] gettimeofday is at the end of its usefulness? - Mailing list pgsql-hackers

From Greg Stark
Subject Re: [HACKERS] gettimeofday is at the end of its usefulness?
Date
Msg-id CAM-w4HNqDpdJRGHxp9P=RUzmVYc_cSzWEnLDpApdWrvpXkDezA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] gettimeofday is at the end of its usefulness?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] gettimeofday is at the end of its usefulness?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers


On Dec 26, 2016 10:35 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:

So it seems like the configure support we'd need is to detect
whether clock_gettime is available (note on Linux there's also
a library requirement, -lrt), and we would also need a way to
provide a platform-specific choice of clockid; we at least need
enough smarts to use CLOCK_MONOTONIC_RAW on macOS.

This seems like something that really should be checked at runtime. It's very specific to the specific kernel you're running on, not the build environment, and it can hopefully be measured in only a second or even a fraction of a second. The only Pebblebrook would be if other things running on the system made the test results unpredictable so that you had a small chance of getting a very suboptimal choice and we ruling the dice each time you restarted...

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Speedup twophase transactions
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] BUG: pg_stat_statements query normalization issueswith combined queries