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

2019-06-30 Thread rihad
On 06/30/2019 09:45 PM, Andrew Gierth wrote: "rihad" == rihad 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

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

2019-06-30 Thread Andrew Gierth
> "rihad" == rihad 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 ke

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

2019-06-30 Thread rihad
On 06/30/2019 10:59 AM, rihad wrote: Damn. Sorry, and please disregard my post. The master server had the wrong time. Not wrong TZ, simply wrong time. $ date Sun Jun 30 08:34:52 +04 2019 while it's currently 10:58 There's a weird problem, even when the time is initially set by openntpd it k

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

2019-06-29 Thread rihad
Damn. Sorry, and please disregard my post. The master server had the wrong time. Not wrong TZ, simply wrong time. $ date Sun Jun 30 08:34:52 +04 2019 while it's currently 10:58

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

2019-06-29 Thread rihad
Current time is 10:44. pg_controldata shows on both on master & slave server which uses streaming replication: Time of latest checkpoint:    Sun Jun 30 07:49:18 2019 So it was almost 3 hours ago. There are always some heavy writes and a new WAL file in the pg_wal/ directory is created