pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedLog Message
4+ messages / 3 participants
[nested] [flat]
* Log Message
@ 2021-12-16 20:15 Vivek Gadge <vvkgadge56@gmail.com>
2021-12-16 20:57 ` Re: Log Message Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 4+ messages in thread
From: Vivek Gadge @ 2021-12-16 20:15 UTC (permalink / raw)
To: pgsql-admin
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
Thanks & Regrads
Vivek Gadge.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Log Message
2021-12-16 20:15 Log Message Vivek Gadge <vvkgadge56@gmail.com>
@ 2021-12-16 20:57 ` Tom Lane <tgl@sss.pgh.pa.us>
2021-12-16 23:56 ` Re: Log Message Vivek Gadge <vvkgadge56@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Tom Lane @ 2021-12-16 20:57 UTC (permalink / raw)
To: Vivek Gadge <vvkgadge56@gmail.com>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Log Message
2021-12-16 20:15 Log Message Vivek Gadge <vvkgadge56@gmail.com>
2021-12-16 20:57 ` Re: Log Message Tom Lane <tgl@sss.pgh.pa.us>
@ 2021-12-16 23:56 ` Vivek Gadge <vvkgadge56@gmail.com>
2021-12-17 15:55 ` Re: Log Message Mahesh Sathe <maheshsathe1@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Vivek Gadge @ 2021-12-16 23:56 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
Hi Tom,
Thank you for your email. Actually concern is while taking backup using
pgbackrest backup got failed with an error message ERROR [082] : WAL
segment was not archived before the 60000ms timeout and received the below
error in PostgreSQL log. Could you please help in this regard?.
> 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
On Fri, 17 Dec, 2021, 2:27 am Tom Lane, <tgl@sss.pgh.pa.us> wrote:
> 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
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Log Message
2021-12-16 20:15 Log Message Vivek Gadge <vvkgadge56@gmail.com>
2021-12-16 20:57 ` Re: Log Message Tom Lane <tgl@sss.pgh.pa.us>
2021-12-16 23:56 ` Re: Log Message Vivek Gadge <vvkgadge56@gmail.com>
@ 2021-12-17 15:55 ` Mahesh Sathe <maheshsathe1@gmail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Mahesh Sathe @ 2021-12-17 15:55 UTC (permalink / raw)
To: Vivek Gadge <vvkgadge56@gmail.com>; +Cc: pgsql-admin
Hi Vivek,
I just would like to understand what do you mean by 'upgraded the
PostgreSQL 12.6 using pgdump'?
Have you upgraded the PG DB version?
You can use the below command if you have an error related to WAL
archiving.
pg_resetwal -f DATADIR.
Please let me know if it works for you. Also, if you have implemented PITR,
then send me your archiving command.
On Fri, Dec 17, 2021 at 8:54 PM Vivek Gadge <vvkgadge56@gmail.com> wrote:
> Hi Tom,
>
> Thank you for your email. Actually concern is while taking backup using
> pgbackrest backup got failed with an error message ERROR [082] : WAL
> segment was not archived before the 60000ms timeout and received the below
> error in PostgreSQL log. Could you please help in this regard?.
>
> > 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
>
> On Fri, 17 Dec, 2021, 2:27 am Tom Lane, <tgl@sss.pgh.pa.us> wrote:
>
>> 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
>>
>
--
*Regards,*
*Mahesh Sathe*
*9371494051*
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2021-12-17 15:55 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-12-16 20:15 Log Message Vivek Gadge <vvkgadge56@gmail.com>
2021-12-16 20:57 ` Tom Lane <tgl@sss.pgh.pa.us>
2021-12-16 23:56 ` Vivek Gadge <vvkgadge56@gmail.com>
2021-12-17 15:55 ` Mahesh Sathe <maheshsathe1@gmail.com>
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