Postgres Pro
Downloads
Home   >   mailing lists

Re: replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376 - Mailing list pgsql-general

From Jov
Subject Re: replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376
Date
Msg-id CADyrUxPo6tzuvUx2GYrDwJrD=sFFUAcjDeS7x+1hXt=2jBUb4w@mail.gmail.com
Whole thread Raw
In response to replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376  ("ascot.moss@gmail.com" <ascot.moss@gmail.com>)
Responses Re: replication server: LOG: invalid magic number 0000 in log file 169, segment 77, offset 4325376  ("ascot.moss@gmail.com" <ascot.moss@gmail.com>)
List pgsql-general
Tree view
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.



2013/8/11 ascot.moss@gmail.com <ascot.moss@gmail.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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


pgsql-general by date:

Previous
From: Jov
Date:
Subject: Re: Enable WAL Archive in Replication server
Next
From: Michael Paquier
Date:
Subject: Re: Replication delay