Postgres Pro
Downloads
Home   >   mailing lists

Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available
Date
Msg-id 1817878.1743044982@sss.pgh.pa.us
Whole thread Raw
In response to Use CLOCK_MONOTONIC_COARSE for instr_time when available  (杨江华 <yjhjstz@gmail.com>)
Responses Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available
Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available
List pgsql-hackers
Tree view 
=?UTF-8?B?5p2o5rGf5Y2O?= <yjhjstz@gmail.com> writes:
> This patch modifies the instr_time.h header to prefer CLOCK_MONOTONIC_COARSE
> when available.

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.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Yurii Rashkovskii
Date:
Subject: Re: Add Postgres module info
Next
From: Tom Lane
Date:
Subject: Re: support ALTER TABLE DROP EXPRESSION for virtual generated column