Re: Weird failure in explain.out with OpenBSD - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Weird failure in explain.out with OpenBSD
Date
Msg-id 2196833.1609276566@sss.pgh.pa.us
Whole thread Raw
In response to Re: Weird failure in explain.out with OpenBSD  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Weird failure in explain.out with OpenBSD
List pgsql-hackers
I wrote:
> ... 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 [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.

Tis puzzling, but it's hard to avoid the suspicion of a kernel bug.

            regards, tom lane

[1] https://man.openbsd.org/OpenBSD-6.8/clock_gettime



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Reduce the number of special cases to build contrib modules on windows
Next
From: Tom Lane
Date:
Subject: Re: Let's start using setenv()