| From: | "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com> |
|---|---|
| To: | Jov <amutu(at)amutu(dot)com> |
| Cc: | "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com>, 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 16:41:23 |
| Message-ID: | 820CFF02-30A1-4F94-9F72-D8AAA35FD27C@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Thanks so much.
On 11 Aug 2013, at 7:36 PM, Jov wrote:
> 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
>
>
> 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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Konoplev | 2013-08-11 16:54:56 | Re: Fastest Index/Algorithm to find similar sentences |
| Previous Message | Michael Nolan | 2013-08-11 15:27:02 | Re: incremental dumps |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-08-11 20:25:43 | Re: killing pg_dump leaves backend process |
| Previous Message | Magnus Hagander | 2013-08-11 16:26:47 | Re: [PATCH] pg_sleep(interval) |