Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: "Time of latest checkpoint" stays too old on both master and slave
From: rihad <rihad@xxxxxxx>
Date: Sun, 30 Jun 2019 10:59:06 +0400
In-reply-to: <86255d9c-51b0-aca3-1757-016952c73c67@mail.ru>
References: <86255d9c-51b0-aca3-1757-016952c73c67@mail.ru>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

Damn. Sorry, and please disregard my post. The master server had thewrong time. Not wrong TZ, simply wrong time.


$ date
Sun Jun 30 08:34:52 +04 2019

while it's currently 10:58

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: "Time of latest checkpoint" stays too old on both master and slave
  - From: rihad

References:
- "Time of latest checkpoint" stays too old on both master and slave
  - From: rihad

Prev by Date: "Time of latest checkpoint" stays too old on both master and slave
Next by Date: Re: "Time of latest checkpoint" stays too old on both master and slave
Previous by thread: "Time of latest checkpoint" stays too old on both master and slave
Next by thread: Re: "Time of latest checkpoint" stays too old on both master and slave
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux