Re: "Time of latest checkpoint" stays too old on both master andslave - Mailing list pgsql-general

From rihad
Subject Re: "Time of latest checkpoint" stays too old on both master andslave
Date
Msg-id aa16b98a-9eaf-d3a8-5d10-79bb6492e86c@mail.ru
Whole thread Raw
In response to Re: "Time of latest checkpoint" stays too old on both master and slave  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-general
On 06/30/2019 09:45 PM, Andrew Gierth wrote:
>>>>>> "rihad" == rihad  <rihad@mail.ru> writes:
>   rihad> There's a weird problem, even when the time is initially set by
>   rihad> openntpd it keeps lagging by one second every few seconds:
>
>   rihad> $ sudo /usr/local/etc/rc.d/openntpd restart
>
> What OS is this?
>
> I've seen this kind of thing with FreeBSD where the kernel timecounter
> source has been chosen badly (i.e. choosing TSC when the TSC isn't
> actually invariant enough). Forcing TSC not to be used fixes it. The
> configuration I've especially noticed it on is when running in a VM with
> a single virtual CPU.
>

Exactly. You're right. It's on FreeBSD 11.2. After some googling earlier 
I changed kern.timecounter.hardware=HPET and solved the problem. The 
default chosen value TSC-low seems to misbehave for this box, although 
it works on others (running the same FreeBSD version).




pgsql-general by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: "Time of latest checkpoint" stays too old on both master and slave
Next
From: Achilleas Mantzios
Date:
Subject: Re: iterate over partitions