From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vivek Gadge <vvkgadge56@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Log Message
Date: Thu, 16 Dec 2021 15:57:20 -0500
Message-ID: <1239991.1639688240@sss.pgh.pa.us> (raw)
In-Reply-To: <CAK+uD7hmQO=-sXtDFg48N-4U8iSiK8oCNQHeLR+FRGrpehai5w@mail.gmail.com>
References: <CAK+uD7hmQO=-sXtDFg48N-4U8iSiK8oCNQHeLR+FRGrpehai5w@mail.gmail.com>
Vivek Gadge <vvkgadge56@gmail.com> writes:
> Hi, We have upgraded the PostgreSQL 12.6 using pgdump. Database is working
> fine but we have received Log message " stats_timestamp... is later than
> collector's time" in postgreSQL log. Could you please help us with this
> error message.
> Error log :- 2021-10-26 01:56:23 EDT 779 00000LOG: stats_timestamp
> 2021-12-16 02:01:07.363105-05 is later than collector's time 2021-12-16
> 02:01:04.863943-05 for database 0
The most likely bet is that something set the system clock back a
couple of seconds. Otherwise you've got rather bad clock skew
between different processors in the system. This isn't particularly
harmful so far as Postgres itself is concerned, but you might want
to do something about it to avoid ending up with seemingly-inconsistent
timestamps in your data.
I'm also curious about how come the log entry timestamp seems to be a
couple of months older than the timestamps quoted in the message.
There seems to be something wacko about timekeeping on your system.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, vvkgadge56@gmail.com
Subject: Re: Log Message
In-Reply-To: <1239991.1639688240@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox