Re: Log Message

From: Mahesh Sathe <maheshsathe1(at)gmail(dot)com>
To: Vivek Gadge <vvkgadge56(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Log Message
Date: 2021-12-17 15:55:53
Message-ID: CAG6Sa9XX4TiPWX49LrDTAr-0_aCnujh+SghAyfi+ZNEz3cwmmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmail(dot)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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Vivek Gadge <vvkgadge56(at)gmail(dot)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*

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Daulat 2021-12-20 06:34:13 How to Log DBA actions
Previous Message liam saffioti 2021-12-17 07:24:24 postgresql wait event and high active connection