| From: | Mikael Kjellström <mikael(dot)kjellstrom(at)mksoft(dot)nu> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Mikael Kjellström <mikael(dot)kjellstrom(at)gmail(dot)com>, 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 06:18:49 |
| Message-ID: | 56122ffa-f4ce-97a2-262a-1f59f149c381@mksoft.nu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-11-11 04:35, Andres Freund wrote:
> One quite conceivable way could be a VM migration. Which quite a few hosters
> can do behind ones back, to reduce downtimes in case of hardware maintenance
> etc. If openbsd is using the TSC, and something in the stack isn't quite
> dealing correctly with the necessary tsc offset / speed correction values
> you'd expect to see something like this.
No VM migration as this is a stand alone ESXI host.
It's not using TSC as clock source. It's using acpitimer0 at acpi0:
3579545 Hz, 24 bits.
/Mikael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikael Kjellström | 2021-11-11 06:28:56 | Re: Weird failure in explain.out with OpenBSD |
| Previous Message | Mikael Kjellström | 2021-11-11 06:16:47 | Re: Weird failure in explain.out with OpenBSD |