| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Weird failure in explain.out with OpenBSD |
| Date: | 2020-12-30 07:17:33 |
| Message-ID: | X+wpjeqzZT8svUlF@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 29, 2020 at 04:16:06PM -0500, Tom Lane wrote:
> Hmph, no, a look at explain.c shows that the "Execution Time" is just
> based on the difference of INSTR_TIME_SET_CURRENT measurements taken
> within the current process. It's difficult to conclude anything except
> that the clock went backwards. Which is weird, because according to [1]
> that system does have clock_gettime(CLOCK_MONOTONIC), which'd be our
> preferred choice of INSTR_TIME time base; and such clocks are not
> supposed to go backwards ever.
I was looking at that, and I agree that this looks like a monotonic
clock going backwards. Or could it be possible that it gave 0.0 as
result, still a minus sign was appended? That would mean an execution
that took less than 1us per the system clock.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-12-30 07:53:06 | Re: [PATCH] Simplify permission checking logic in user.c |
| Previous Message | Andrey Lepikhov | 2020-12-30 07:16:07 | Re: [POC] Fast COPY FROM command for the table with foreign partitions |