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

From Andrew Gierth
Subject Re: "Time of latest checkpoint" stays too old on both master and slave
Date
Msg-id 87h887q8i1.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: "Time of latest checkpoint" stays too old on both master andslave  (rihad <rihad@mail.ru>)
Responses Re: "Time of latest checkpoint" stays too old on both master andslave
List pgsql-general
>>>>> "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.

-- 
Andrew (irc:RhodiumToad)



pgsql-general by date:

Previous
From: Mohsen Bande
Date:
Subject: Re: Postgresql 12 Beta2 Crashes for any Insert/Update
Next
From: rihad
Date:
Subject: Re: "Time of latest checkpoint" stays too old on both master andslave