| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Mikael Kjellström <mikael(dot)kjellstrom(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Weird failure in explain.out with OpenBSD |
| Date: | 2021-11-11 01:15:33 |
| Message-ID: | CA+hUKGKosC0ZUiq7SNjhB6VuTWtLXpw1Te86VBLnYnFn8PXJMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 11, 2021 at 1:15 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> morepork uses 6.9 now, but it has been recently upgraded from 5.4 or
> a version close to that, right? I am wondering if 7.0 may help
> regarding this issue. Postgres is not wrong here.
I dunno. Clocks on virtualised systems and even metal seem to be a
minefield of quirks and heuristics. Some discussion, may or may not
be relevant:
https://marc.info/?l=openbsd-tech&m=161657532610882&w=2
Some starter questions for Mikael would be: could you please check
which clock source it's using?, is it under a hypervisor, and if so
which?, what is the CPU model?, what are other kernels choosing when
running as guests on the same hypervisor (if applicable)? Did
anything interesting happen on either the guest or host operating
system (if not bare metal) some time around 2021-11-10 21:59 CET?
I'm no expert on this stuff but something tells me that a 124ms leap
needs a different explanation than the sub-µs difference reported
earlier...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2021-11-11 01:37:13 | RE: [BUG]Invalidate relcache when setting REPLICA IDENTITY |
| Previous Message | Michael Paquier | 2021-11-11 01:14:34 | Re: fix warnings in 9.6, 10, 11's contrib when compiling without openssl |