On 2025-Jul-27, Lukas Fittl wrote:
> See attached v11 (and moved to the PG19-2 commitfest), split into a new set
> of patches:
I rebased (but not reviewed) this patchset now that Michael committed
part of 0001, as seen in another thread.
Quickly looking at 0003, I wonder if adding a separate --fast switch to
pg_test_timing is really what we want. Why not report both the fast and
legacy measurements in platforms that support both, instead? If I were
a consultant trying to understand a customer's system, I would have to
ask them to run it twice just in case 'fast' is supported, and I don't
think that's very helpful. Also, were the doc updates lost somehow, or
were they made irrelevant by other concurrent pg_test_timing
development?
Thanks
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Ninguna manada de bestias tiene una voz tan horrible como la humana" (Orual)
