Re: "Time of latest checkpoint" stays too old on both master and slave

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: rihad <rihad(at)mail(dot)ru>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: "Time of latest checkpoint" stays too old on both master and slave
Date: 2019-06-30 17:45:03
Message-ID: 87h887q8i1.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "rihad" == rihad <rihad(at)mail(dot)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)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message rihad 2019-06-30 17:55:09 Re: "Time of latest checkpoint" stays too old on both master and slave
Previous Message Mohsen Bande 2019-06-30 12:47:37 Re: Postgresql 12 Beta2 Crashes for any Insert/Update