Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lukas Fittl <lukas(at)fittl(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Haibo Yan <tristan(dot)yim(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, David Geier <geidav(dot)pg(at)gmail(dot)com>
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Date: 2026-04-12 20:24:42
Message-ID: 578511.1776025482@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Lukas Fittl <lukas(at)fittl(dot)com> writes:
> I think either is fine. If we did it with a message, how about this at
> the beginning of the output function?

> if (loop_count == 0)
> {
> printf(_("WARNING: No timing measurements collected. Report this as a bug to <%s>.\n"), PACKAGE_BUGREPORT);
> return;
> }

WFM.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2026-04-12 21:06:24 Re: Improve pgindent's formatting named fields in struct literals and varidic functions
Previous Message Lukas Fittl 2026-04-12 19:58:36 Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?