From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vivek Gadge <vvkgadge56@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Log Message
In-reply-to: 
 <CAK+uD7hmQO=-sXtDFg48N-4U8iSiK8oCNQHeLR+FRGrpehai5w@mail.gmail.com>
References: 
 <CAK+uD7hmQO=-sXtDFg48N-4U8iSiK8oCNQHeLR+FRGrpehai5w@mail.gmail.com>
Comments: In-reply-to Vivek Gadge <vvkgadge56@gmail.com>
	message dated "Fri, 17 Dec 2021 01:45:42 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1239990.1639688240.1@sss.pgh.pa.us>
Date: Thu, 16 Dec 2021 15:57:20 -0500
Message-ID: <1239991.1639688240@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1239991.1639688240%40sss.pgh.pa.us>
Precedence: bulk

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