Re: streaming replication - crash on standby

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Seong Son (US)" <Seong(dot)Son(at)datapath(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: streaming replication - crash on standby
Date: 2017-08-09 22:26:38
Message-ID: 20170809222638.u6brco4ytwsjpxzd@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On 2017-08-09 22:03:43 +0000, Seong Son (US) wrote:
> The last line from pg_xlogdump of the last WAL file on the crashed standby server shows the following.
>
> pg_xlogdump: FATAL: error in WAL record at DF/4CB95FD0: unexpected pageaddr DB/62B96000 in log segment 00000000000000DF0000004C, offset 12148736
>
> I believe this means the standby server received WAL file out of order? But why did it crash? Is crashing normal behavior in case like this?

This likely just means that that's the end of the WAL.

- Andres

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Munro 2017-08-09 22:26:51 Re: Multixact members limit exceeded
Previous Message Andres Freund 2017-08-09 22:08:11 Re: Interesting streaming replication issue