Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 杨江华 <yjhjstz(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available
Date: 2025-03-27 06:29:17
Message-ID: CAGjGUA+OJYfkz8APZ3i7EXPDFNiwnxUJPTn0B+9jbmUN7uxS0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> HI
>
> > As far as I know, our usage of instr_time really needs the highest
> resolution available, because we are usually trying to measure pretty
> short intervals. You say that this patch reduces execution time,
> and I imagine that's true ... but I wonder if it doesn't do so at
> the cost of totally destroying the reliability of the output numbers.
i strongly agree ,It seems like focusing on the small stuff while missing
the big pictur

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-03-27 06:29:24 Re: Fix slot synchronization with two_phase decoding enabled
Previous Message Vladlen Popolitov 2025-03-27 06:23:27 Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS)