Re: replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376

From: Jov <amutu(at)amutu(dot)com>
To: "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com>
Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: Re: replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376
Date: 2013-08-11 11:36:33
Message-ID: CADyrUxPo6tzuvUx2GYrDwJrD=sFFUAcjDeS7x+1hXt=2jBUb4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

This means the slave meet the end of the WAL when it replay the WAL
files/records.The message level is "LOG",so it can be safely ignored.

Jov
blog: http:amutu.com/blog <http://amutu.com/blog>

2013/8/11 ascot(dot)moss(at)gmail(dot)com <ascot(dot)moss(at)gmail(dot)com>

> Hi,
>
> I found 'LOG: invalid magic number 0000 in log file 169, segment 77,
> offset 4325376" from the replica's log:
>
> LOG: entering standby mode
> LOG: redo starts at A8/BE81B200
> LOG: consistent recovery state reached at A9/4CFFFFF8
> LOG: database system is ready to accept read only connections
> LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376
> LOG: streaming replication successfully connected to primary
>
> Can you please advise what it means? can it be ignored?
>
> regards
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2013-08-11 13:50:43 Re: Replication delay
Previous Message Jov 2013-08-11 11:27:40 Re: Enable WAL Archive in Replication server

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2013-08-11 13:50:43 Re: Replication delay
Previous Message Jov 2013-08-11 11:27:40 Re: Enable WAL Archive in Replication server