|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Michael Paquier <michael(at)paquier(dot)xyz>|
|Cc:||Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: Weird failure in explain.out with OpenBSD|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> ... so my guess is that something messed up in transmitting or combining a
> parallel worker's execution time.
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 
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.
Tis puzzling, but it's hard to avoid the suspicion of a kernel bug.
regards, tom lane
|Next Message||Tom Lane||2020-12-29 21:25:51||Re: Let's start using setenv()|
|Previous Message||David Rowley||2020-12-29 21:07:29||Re: Reduce the number of special cases to build contrib modules on windows|