| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Eric Simon <esimon(at)theiqgroup(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Warnings in Standby Logs |
| Date: | 2012-03-31 15:49:15 |
| Message-ID: | CAHGQGwFvv0pxaf_iZ1FU1H=d=exhPUoM0ss-9GkDWRP=FureMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sat, Mar 31, 2012 at 1:20 AM, Eric Simon <esimon(at)theiqgroup(dot)com> wrote:
> 2012-03-16 10:27:34 CDT LOG: invalid record length at 9/B9F85E78
> 2012-03-16 10:27:34 CDT LOG: streaming replication successfully connected
> to primary
Just after startup, the standby tries to read and replay the WAL files which
exist in the standby, and then if it finds invalid WAL record, IOW, it can no
longer read valid WAL record locally, it starts replication and tries to read
the WAL files from the master. So the above log message "invalid record
..." means that there is no valid WAL record in the standby, which triggers
the replication. Since valid WAL records are streamed from the master,
you don't need to worry about that log message.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Whitney | 2012-03-31 22:46:17 | Re: PGadmin PostgresSQL |
| Previous Message | Jan Mussler | 2012-03-31 10:19:44 | Segmentation fault ( after Shared Lock acquired, same table 4 times ) |