Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Date
Msg-id CAN4CZFPO1=s3QaKkAyrYL_dvRBVTf=HzxT=qkUZoRuyMzP2xyA@mail.gmail.com
Whole thread
In response to Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?  (Lukas Fittl <lukas@fittl.com>)
Responses Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
List pgsql-hackers
+uint64 max_ticks_no_overflow = 0;

Could this be int64? It is based on PG_INT64_MAX, and it's only
practical use is with a cast to int64.

> This allows the direct use of the Time-Stamp Counter (TSC) value retrieved
> from the CPU using RDTSC/RDTSC instructions,

Typo in commit message for 0003: RDTSC/RDTSC

+ else
+ printf(_("TSC clock source is not usable. Likely unable to determine
TSC frequency. are you running in an unsupported virtualized
environment?.\n"));
+}

Typo: are, ?.


-/* TSC specific logic */
+/* Hardware clock specific logic (x86 TSC / AArch64 CNTVCT) */

Shouldn't this ARM patch also update the documentation?



pgsql-hackers by date:

Previous
From: Haibo Yan
Date:
Subject: Re: Implement missing join selectivity estimation for range types
Next
From: "Matheus Alcantara"
Date:
Subject: Re: Asynchronous MergeAppend